dev@lucene.apache.org
> Subject: RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of
> sync
>
> I tried this, and the test fails under Maven; codec's class is
> o.a.l.index.codecs.lucene3x.Lucene3xCodec instead of
> o.a.l.index.codecs.preflexrw.PreFlexRWCodec.
>
-
> From: Steven A Rowe [mailto:sar...@syr.edu]
> Sent: Monday, November 21, 2011 2:40 PM
> To: dev@lucene.apache.org
> Subject: RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of
> sync
>
> Thanks, I'll give it a try. - Steve
>
> > -Original Messag
Thanks, I'll give it a try. - Steve
> -Original Message-
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Monday, November 21, 2011 2:38 PM
> To: dev@lucene.apache.org
> Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of
> sync
>
>
e is
>> the only failing test.
>>
>>
>>
>> Maybe there is a Maven-specific test classpath ordering problem here?
>>
>>
>>
>> Steve
>>
>>
>>
>> From: Shai Erera [mailto:ser...@gmail.com]
>> Sent: Monday, November
Maven-specific test classpath ordering problem here?
Steve
From: Shai Erera [mailto:ser...@gmail.com]
Sent: Monday, November 21, 2011 11:13 AM
To: dev@lucene.apache.org
Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of sync
Perhaps it's a build error (i.e
module’s TextIndexClose is the only
failing test.
Maybe there is a Maven-specific test classpath ordering problem here?
Steve
From: Shai Erera [mailto:ser...@gmail.com]
Sent: Monday, November 21, 2011 11:13 AM
To: dev@lucene.apache.org
Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303
Perhaps it's a build error (i.e. not cleaning after the test)? This is the
exception that appears in the log:
The following exceptions were thrown by threads:
*** Thread: Lucene Merge Thread #0 ***
org.apache.lucene.index.MergePolicy$MergeException:
java.lang.IllegalStateException: sub-readers hav
