No, I gave up making Jackrabbit compatible with a newer Lucene version.
But then, I had to be able to work with a modern Lucene in the rest of
my app.
I simply renamed all lucene packages in something like
"org.apache.jackrabbit.org.apache.lucene", modified all related
Jackrabbit classed and
Ok i understand the function of shading the lucene packages
but that brings me not really to a newer lucene version in jackrabbit-core.
We are only using jackrabbit itself and do not have an newer lucene version
in our application or do you think to index the content with a newer lucene
Hi Cédric
>As a workaround, I shadowed the Lucene's 3.6 lib by changing its package
>name, so that it may get along with a more recent version.
>And then after a while, I moved toward a Solr server, and then had not
>the need of shadowing anymore, so I put back the original 3.6 lib.
Can you
You are right it was requested years ago .. I think it's work but not
impossible .. hopefully :-)
Maybe i do not understand your idea .. What ist the plan with a shaded jar file
?
How would it help to upgrade to a newer version ?
thanks
claus
>I understand what you'd like to do, but there's a
Hi !
If i understand you right i have not the problem to use 2 different versions of
lucene in the same project.
My goal is to update the lucene library in jackrabbit itself.
This means also maybe a migration path or a rebuild (that would be ok for me
personally) to a newer lucene index inside
