[
https://issues.apache.org/jira/browse/LUCENE-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463765#comment-13463765
]
Steven Rowe commented on LUCENE-4435:
-------------------------------------
Yeah, I have a note in {{dev-tools/maven/README.maven}}:
{quote}
Note: if you change the version in the POMs, there is one test method
that will fail under maven-surefire-plugin:
o.a.l.index.TestCheckIndex#testLuceneConstantVersion(). It's safe to
@Ignore this test method, since it's just comparing the value of the
lucene.version system property (set in the maven-surefire-plugin
configuration in the lucene-core POM) against a hard-wired official
version (o.a.l.util.Constants.LUCENE_MAIN_VERSION).
{quote}
> rethink TestCheckIndex.testLuceneConstantVersion
> ------------------------------------------------
>
> Key: LUCENE-4435
> URL: https://issues.apache.org/jira/browse/LUCENE-4435
> Project: Lucene - Core
> Issue Type: Bug
> Components: general/test
> Reporter: Robert Muir
>
> This test currently checks the "display version" of lucene which is set by
> the ant build.xml variable.
> But its been problematic in the past: and I'm sure its annoying for people
> running from things like IDEs.
> I think LUCENE-4428 is a more straightforward way of checking that the
> version is set correctly, it verifies the actual JAR metadata.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
