[
https://issues.apache.org/jira/browse/LUCENE-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786499#action_12786499
]
Simon Willnauer commented on LUCENE-2100:
-----------------------------------------
bq. Simon what do you suggest? Instead of breaking in 3.1
I suggest to move the core analyzer into a separate issue and link those. That
way we can make progress here as the bw policy is not that strict or people do
not care that much than they do for core analyzers. I doubt that many people
have subclassed StandardAnalyzer and if they do they might do something wrong
though. Lets have two issues so we can drive the discussion independently from
contrib.
My personal feeling is that we should break it in 3.1 lets see what the other
devs object.
> Make contrib analyzers final
> ----------------------------
>
> Key: LUCENE-2100
> URL: https://issues.apache.org/jira/browse/LUCENE-2100
> Project: Lucene - Java
> Issue Type: Improvement
> Components: contrib/analyzers
> Affects Versions: 1.9, 2.0.0, 2.1, 2.2, 2.3, 2.3.1, 2.3.2, 2.4, 2.4.1,
> 2.9, 2.9.1, 3.0
> Reporter: Simon Willnauer
> Priority: Minor
> Fix For: 3.1
>
>
> The analyzers in contrib/analyzers should all be marked final. None of the
> Analyzers should ever be subclassed - users should build their own analyzers
> if a different combination of filters and Tokenizers is desired.
--
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
