[
https://issues.apache.org/jira/browse/LUCENE-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767463#action_12767463
]
Robert Muir commented on LUCENE-1987:
-------------------------------------
bq. The problem is that this is not very different from saying "the onus is on
the user to call the setXYZ method to get back to the old buggy behavior",
which at least last time we discussed back-compat was controversial (ie, it's a
change to our drop-in back-compat policy).
Michael, yes I agree with you. What I am wondering is: is it really working in
practice/in spirit? Forcing the user to supply the version, well it does make
them look at the warning in the Version class, which is good. But nothing
stops them from just using CURRENT.
{noformat}
Use this to get the latest & greatest settings, bug fixes, etc, for Lucene.
{noformat}
followed by the big bold warning about backwards compatibility. just curious
what most users are doing, sacrificing drop-in for "latest and greatest?"
I do think we should do things to improve contrib analyzers that are still
stuck with this buggy behavior at some point: i.e LUCENE-1373.
But maybe we don't need the Version with contrib analyzers, since you should be
able to use an older lucene-analyzers jar file with new lucene if you want the
back compat????
(sorry to stray somewhat off-topic)
> Remove rest of analysis deprecations (Token, CharacterCache)
> ------------------------------------------------------------
>
> Key: LUCENE-1987
> URL: https://issues.apache.org/jira/browse/LUCENE-1987
> Project: Lucene - Java
> Issue Type: Task
> Components: Analysis
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 2.9.1, 3.0
>
> Attachments: LUCENE-1987-StopFilter-backport29.patch,
> LUCENE-1987-StopFilter-BW.patch, LUCENE-1987-StopFilter.patch,
> LUCENE-1987-StopFilter.patch, LUCENE-1987-StopFilter.patch,
> LUCENE-1987-StopFilter.patch, LUCENE-1987.patch, LUCENE-1987.patch,
> LUCENE-1987.patch
>
>
> These removes the rest of the deprecations in the analysis package:
> - -Token's termText field-- (DONE)
> - -eventually un-deprecate ctors of Token taking Strings (they are still
> useful) -> if yes remove deprec in 2.9.1- (DONE)
> - -remove CharacterCache and use Character.valueOf() from Java5- (DONE)
> - Stopwords lists
> - Remove the backwards settings from analyzers (acronym, posIncr,...). They
> are deprecated, but we still have the VERSION constants. Do not know, how to
> proceed. Keep the settings alive for index compatibility? Or remove it
> together with the version constants (which were undeprecated).
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
