[
https://issues.apache.org/jira/browse/LUCENE-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032425#comment-15032425
]
Christine Poerschke commented on LUCENE-6911:
---------------------------------------------
Change committed, deprecating the broken no-op getter.
How would removal of the deprecated method work, just "remove ... method"
instead of "deprecate ... method" in the API Changes section of CHANGES.txt and
commit/merge as usual? Or should removal be done only for {{trunk}} but not
{{branch_5x}}?
> StandardQueryParser's getMultiFields(CharSequence[] fields) method is a no-op
> -----------------------------------------------------------------------------
>
> Key: LUCENE-6911
> URL: https://issues.apache.org/jira/browse/LUCENE-6911
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
> Fix For: Trunk, 5.4
>
> Attachments: LUCENE-6911.patch
>
>
> problem summary:
> *
> {{lucene.queryparser.flexible.standard.StandardQueryParser.getMultiFields(CharSequence[]
> fields)}} is a no-op
> details:
> * https://scan.coverity.com/projects/5620 mentioned on the dev mailing list
> (http://mail-archives.apache.org/mod_mbox/lucene-dev/201507.mbox/%3ccaftwexg51-jm_6mdeoz1reagn3xgkbetoz5ou_f+melboo1...@mail.gmail.com%3e)
> in July 2015:
> ** coverity CID 120698
--
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
