[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130803#comment-14130803
]
Uwe Schindler edited comment on LUCENE-5939 at 9/11/14 10:08 PM:
-----------------------------------------------------------------
bq. So then I checked lucene/common-build.xml, and version is indeed set to
4.9-SNAPSHOT. I then downloaded the official source release, and there too the
version was 4.9-SNAPSHOT.
This is correct. When we build the release artifacts, the version is
overwritten with -Dversion=xxxx. If you build lucene from source you always
have SNAPSHOT versions. This is done to differentiate then from "official
builds". "lucene.version" is a metadata field that is initialized with the
"human-readable version", which now disappeared in 4.10, because we no longer
read the JAR manifest.
was (Author: thetaphi):
bq. So then I checked lucene/common-build.xml, and version is indeed set to
4.9-SNAPSHOT. I then downloaded the official source release, and there too the
version was 4.9-SNAPSHOT.
This is correct. When we build the release artifacts, the version is
overwritten with -Dversion=xxxx. If you build lucene from source you always
have SNAPSHOT versions. This is done to differentiate then from "official
builds". "lucene.version" is a metadata field that is initialized with the
"human-readable version", which now disappeared..
> 4.10.1 cannot read 4.10 indexes
> -------------------------------
>
> Key: LUCENE-5939
> URL: https://issues.apache.org/jira/browse/LUCENE-5939
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Priority: Blocker
>
> Thank you mike for the smoketester addition. It failed because 4.10.1 was not
> verifying backwards compatibility against 4.10
> However, when i added the indexes (svn copied from branch-4x), the test fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
