[ 
https://issues.apache.org/jira/browse/LUCENE-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857498#action_12857498
 ] 

DM Smith commented on LUCENE-2396:
----------------------------------

{quote}
bq. One mechanism that would work is versioned Java package names or class 
names. The current release would get the good names. If a user wanted the old 
jar they'd have to get it from the current release (e.g. 
lucene-analyzers-3.5_3.0.jar) and then change their code to use the old stuff 
which now has either a new package name or a new class name. Example, 
trStemmer.java is going to be changed as the first breaking change since 3.0, 
so trStemmer3_0.java is created as a copy and then trStemmer.java is changed.

Right, but I dont think Lucene should manage this. I think if we assume 
"normally versioned releases", a user with a really complex case that needs 
multiple versions of lucene working in the same JVM , like you, could use some 
other tool (eclipse refactor or maybe google's jarjar) to do rename things?
{quote}

I can go along with this.

I still think it might be good to let the dust settle on the general Version 
question before committing.

> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to