m:Uwe Schindler
> Sent: Thursday 30th January 2014 14:48
> To: java-user@lucene.apache.org
> Subject: RE: LUCENE-5388 AbstractMethodError
>
> Hi Markus,
>
> Lucene trunk has a backwards incompatible API, so Analyzers compiled with
> Lucene 4.6 cannot be used on Lucene trunk
index.io]
> Sent: Thursday, January 30, 2014 12:52 PM
> To: java-user@lucene.apache.org
> Subject: RE: LUCENE-5388 AbstractMethodError
>
> Hi Uwe,
>
> The bug occurred only after LUCENE-5388 was committed to trunk, looks like
> its the changes to Analyzer and friends. The ful
gt; We test trunk with our custom stuff as well, but all our custom stuff is
> nicely built with Maven against the most recent release of Solr and/or
> Lucene. If that stays a problem we may have to build stuff against
> branch_4x instead.
>
> Thanks,
> Markus
>
> -Original mes
D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From: Markus Jelsma [mailto:markus.jel...@openindex.io]
> > Sent: Thursday, January 30, 2014 10:50 AM
> > To: java-user@lucene.apache.org
> > Subject: LUCENE-538
us.jel...@openindex.io]
> Sent: Thursday, January 30, 2014 10:50 AM
> To: java-user@lucene.apache.org
> Subject: LUCENE-5388 AbstractMethodError
>
> Hi,
>
> Apologies for cross posting; i got no response on the Sorl list.
>
> We have a developement environment running trun
Hi,
Apologies for cross posting; i got no response on the Sorl list.
We have a developement environment running trunk but have custom analyzers and
token filters built on 4.6.1. Now the constructors have changes somewhat and
stuff breaks. Here's a consumer trying to get a TokenStream from an An
