[jira] [Commented] (LUCENE-5632) transition Version constants from LUCENE_MN to LUCENE_M_N

["Uwe Schindler (JIRA)" <ji...@apache.org>]

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

Uwe Schindler commented on LUCENE-5632:
---------------------------------------

One idea. We redfine the enum with the new syntax. In Lucene 4.x we may additionally define the old constants as additional alias statics (+ deprecated) inside the enum? Java does not allow additional constants in an enum that are identical to others, but we can maybe move the deprecated ones between the real ones (like: {{LUCENE_4_0, @Deprecated LUCENE_40, LUCENE_4_1, @Deprecated LUCENE_41}}, although I am not sure if they should come before or after).
We must also fix the parseVersionLenient for use by Solr + ElasticSearch.

> transition Version constants from LUCENE_MN to LUCENE_M_N
> ---------------------------------------------------------
>
>                 Key: LUCENE-5632
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5632
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>
> We should fix this, otherwise the constants will be hard to read (e.g. Version.LUCENE_410, is it 4.1.0 or 4.10 or whatever).
> I do not want this to be an excuse for an arbitrary 5.0 release that does not have the features expected of a major release :)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org