> The problem are not the class names, the problem are the names as
> written to Index. And in a Lucene 4 index there is written e.g., "Lucene47"
> as Codec and Postingsformat. The lookup by name is done by this name.
> IndexReader/Writer does Codec.forName("Lucene47"). For this to work,
> every co
Hi,
> On Mon, Jul 6, 2015 at 4:32 PM, Uwe Schindler wrote:
> > Hi,
> >
> > It could be the reason for this is your classpath:
> >
> > If you load all Lucene Versions into the same classloader (but with
> > different
> package names - I assume you use Maven Shade plugin to do this), Lucene 3
> wi
On Mon, Jul 6, 2015 at 4:32 PM, Uwe Schindler wrote:
> Hi,
>
> It could be the reason for this is your classpath:
>
> If you load all Lucene Versions into the same classloader (but with different
> package names - I assume you use Maven Shade plugin to do this), Lucene 3
> will load perfectly, y
Hi,
It could be the reason for this is your classpath:
If you load all Lucene Versions into the same classloader (but with different
package names - I assume you use Maven Shade plugin to do this), Lucene 3 will
load perfectly, yes; Lucene 4 will also load perfectly, yes! But when it tries
to
