You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "DM Smith (JIRA)" <ji...@apache.org> on 2010/04/15 20:16:50 UTC
[jira] Issue Comment Edited: (LUCENE-2396) remove version from
contrib/analyzers.
[ https://issues.apache.org/jira/browse/LUCENE-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857456#action_12857456 ]
DM Smith edited comment on LUCENE-2396 at 4/15/10 2:16 PM:
-----------------------------------------------------------
{quote}
So I think we should instead use real-versions for contrib/analyzers. You can be damn sure if you stick with lucene-analyzers-3.0.jar that your stemmer isn't going to change behavior... no matter how much backwards stuff we try to add, this is easiest and safest on everyone.
{quote}
I could live with that....maybe. What guarantee is there that lucene-analyzers-3.0.jar will work with lucene-core-3.7.jar? How does that work?
How can I use lucene-analyzers-3.0.jar on old indexes and lucene-analyzers-3.5.jar on newer ones within the same application?
What I'd like to see is that all analyzers and their parts are kept together in an analyzer jar (maybe more than one for the honking big analyzers as we have today) and that it be elevated to core. (I think contrib give the wrong impression.) And have a well-define compatibility policy.
was (Author: dmsmith):
{quote}
So I think we should instead use real-versions for contrib/analyzers. You can be damn sure if you stick with lucene-analyzers-3.0.jar that your stemmer isn't going to change behavior... no matter how much backwards stuff we try to add, this is easiest and safest on everyone.
{quote}
I could live with that....maybe. What guarantee is there that lucene-analyzers-3.0.jar will work with lucene-core-3.7.jar? How does that work?
How can I use lucene-analyzers-3.0.jar on old indexes and lucene-analyzers-3.5.jar on newer ones within the same package?
What I'd like to see is that all analyzers and their parts are kept together in an analyzer jar (maybe more than one for the honking big analyzers as we have today) and that it be elevated to core. (I think contrib give the wrong impression.) And have a well-define compatibility policy.
> remove version from contrib/analyzers.
> --------------------------------------
>
> Key: LUCENE-2396
> URL: https://issues.apache.org/jira/browse/LUCENE-2396
> Project: Lucene - Java
> Issue Type: Task
> Components: contrib/analyzers
> Affects Versions: 3.1
> Reporter: Robert Muir
> Assignee: Robert Muir
> Attachments: LUCENE-2396.patch
>
>
> Contrib/analyzers has no backwards-compatibility policy, so let's remove Version so the API is consumable.
> if you think we shouldn't do this, then instead explicitly state and vote on what the backwards compatibility policy for contrib/analyzers should be instead, or move it all to core.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org