lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] Created: (LUCENE-2004) Constants.LUCENE_MAIN_VERSION is inlined in code compiled against Lucene JAR, so version detection is incorrect
Date Thu, 22 Oct 2009 06:23:59 GMT
Constants.LUCENE_MAIN_VERSION is inlined in code compiled against Lucene JAR, so version detection
is incorrect
---------------------------------------------------------------------------------------------------------------

                 Key: LUCENE-2004
                 URL: https://issues.apache.org/jira/browse/LUCENE-2004
             Project: Lucene - Java
          Issue Type: Bug
    Affects Versions: 2.9
            Reporter: Uwe Schindler
            Assignee: Uwe Schindler
             Fix For: 2.9.1, 3.0


When you compile your own code against the Lucene 2.9 version of the JARs and use the LUCENE_MAIN_VERSION
constant and then run the code against the 3.0 JAR, the constant still contains 2.9, because
javac inlines primitives and Strings into the class files if they are public static final
and are generated by a constant (not method).

The attached fix will fix this by using a ident(String) functions that return the String itsself
to prevent this inlining.

Will apply to 2.9, trunk and 2.9 BW branch. No I can also reenable one test I removed because
of this.

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


Mime
View raw message