You can have your own shaded version of the lucene 3.6 jars. We're doing just that with the oak-lucene artifact, as we use elasticsearch which is using a much more recent version of lucene in the same project. I can't give exact details on how to set up the maven artifact for the old jackrabbit version. Here's the pom file for the oak-lucene-shaded artifact for oak at least: https://github.com/tveimo/oak-lucene-shaded
On Tue, 12 May 2020 at 20:56, KÖLL Claus <c.ko...@tirol.gv.at> wrote: > > Hi @ all.. > > > > I hope some „old“ jackrabbit developers will participate to this dicussion. > > We are using jackrabbit as a plain dms over years now. It is a central > component in our infrastructure and we are really satisfiying with it. > > > > We are not planning to migrate to jackrabit oak as we have no requirements to > new features. > > I know that jackrabbit is in maintenance mode, but 3’rd party libraries will > still be upgradet to the newest versions (primarily thanks to julian). > > > > We will use jackrabbit surely for the next years but one thing worries me. > The strong integration of lucene in jackrabbit makes it really difficult to > upgrade to a newer version. > > As you all know we are using lucene 3.6 and it is in the meanwhile really > outdatet. > > I’m no lucene expert but i have tried to upgrade to version 4 as the first > step. > > > > As there are many api changes it’s not really easy. > > > > Maybe some jackrabbit developers which have written the code give some > estimates what it would mean to upgrade to a newer version. > > > > Thanks for any input ! > > > > greets > > Claus > > > > -- -Tor
