[
https://issues.apache.org/jira/browse/LUCENE-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983644#comment-13983644
]
Uwe Schindler commented on LUCENE-5632:
---------------------------------------
In fact it is possible to add "deprecated" old constants somewhere at the end
of the enum. Those are no real enum constants (they dont work in switch
statements), but for the general use case of matchVersion parameters, this is
fine:
{code:java}
@Deprecated
public static final Version LUCENE_41 = LUCENE_4_1;
{code}
> 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: [email protected]
For additional commands, e-mail: [email protected]
