@lucene.apache.org
> Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync
>
> I figured this would happen. I saw quite a few places that are "4.0.0"
> in the maven files, but it wasnt obvious to me which one was the one i should
> change.
>
> I
Maven uses major.minor.bugfix format for versioning. I don't think it
can be changed.
Dawid
On Wed, May 30, 2012 at 4:47 PM, Robert Muir wrote:
> I figured this would happen. I saw quite a few places that are "4.0.0"
> in the maven files, but it wasnt obvious to me which one was the one i
> shou
I just committed a fix: it was a version property in build.xml
-Original Message-
From: Robert Muir [mailto:rcm...@gmail.com]
Sent: Wednesday, May 30, 2012 10:48 AM
To: dev@lucene.apache.org
Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync
I figured this would
I figured this would happen. I saw quite a few places that are "4.0.0"
in the maven files, but it wasnt obvious to me which one was the one i
should change.
I think this is because maven internally has "4.0.0" as the version of
some files.
Does anyone know? I think we should add an xml comment ab
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/504/
1 tests failed.
REGRESSION: org.apache.lucene.index.TestCheckIndex.testLuceneConstantVersion
Error Message:
Invalid version: 4.0-SNAPSHOT
Stack Trace:
java.lang.AssertionError: Invalid version: 4.0-SNAPSHOT
at
__randomiz
