[
https://issues.apache.org/jira/browse/LUCENE-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981640#action_12981640
]
Simon Willnauer commented on LUCENE-2867:
-----------------------------------------
bq. Here is the patch that deprecates methods using CharSequence. Can someone
please review if I did the API deprecation correctly?
those comments and annotations look good!
bq. I was thinking initially that deprecated methods would be removed on
version 4, I'm not sure anymore. Will it be removed on 4 or 3.1?
you should drop those methods from 4.0 code if you want to deprecate. Since
this is a contrib you don't necessarily need to deprecate so you could alo drop
them from 3.1 or even from 3.0.x
> Change contrib QP API that uses CharSequence as string identifier
> -----------------------------------------------------------------
>
> Key: LUCENE-2867
> URL: https://issues.apache.org/jira/browse/LUCENE-2867
> Project: Lucene - Java
> Issue Type: Improvement
> Components: contrib/*
> Affects Versions: 3.0.3
> Reporter: Adriano Crestani
> Priority: Minor
> Fix For: 3.0.4
>
> Attachments: lucene_2867_adriano_crestani_2011_01_13.patch
>
>
> There are some API methods on contrib queryparser that expects CharSequence
> as identifier. This is wrong, since it may lead to incorrect or mislead
> behavior, as shown on LUCENE-2855. To avoid this problem, these APIs will be
> changed and enforce the use of String instead of CharSequence on version 4.
> This patch already deprecate the old API methods and add new substitute
> methods that uses only String.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
