[
https://issues.apache.org/jira/browse/SOLR-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310643#comment-15310643
]
ASF subversion and git services commented on SOLR-9161:
-------------------------------------------------------
Commit 245e4839d1e50ed05a59a2f2ee82be713cc7e6fc in lucene-solr's branch
refs/heads/master from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=245e483 ]
Revert "SOLR-9161: SolrPluginUtils.invokeSetters now accommodates setter
variants"
This reverts commit 50658dd93d16eec37e906a24446146609cc93706.
Conflicts:
solr/CHANGES.txt
> SolrPluginUtils.invokeSetters should accommodate setter variants
> ----------------------------------------------------------------
>
> Key: SOLR-9161
> URL: https://issues.apache.org/jira/browse/SOLR-9161
> Project: Solr
> Issue Type: Bug
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
> Priority: Minor
> Attachments: SOLR-9161.patch
>
>
> The code currently assumes that there is only one setter (or if there are
> several setters then the first one found is used and it could mismatch on the
> arg type).
> Context and motivation is that a class with a
> {code}
> void setAFloat(float val) {
> this.val = val;
> }
> {code}
> setter may wish to also provide a
> {code}
> void setAFloat(String val) {
> this.val = Float.parseFloat(val);
> }
> {code}
> convenience setter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
