Just to add; I wouldn't move any project onto the old jackrabbit codebase. And you can use oak without lucene at all, just use the property indexes. You simply avoid including the oak-lucene dependencies.
On Sun, 10 Oct 2021 at 19:14, Torgeir Veimo <torgeir.ve...@gmail.com> wrote: > > You can build a modified version of oak with shaded lucene > dependencies, so they don't interfere with other lucene dependencies > in your project. See the example pom.xml at > https://github.com/tveimo/oak-mega-shaded > > That particular dependency can be tries out with gradle using > implementation 'com.github.tveimo:oak-mega-shaded:4ebfa176f1' > > It doesn't use the latest oak version at the moment, but I will > upgrade it shortly. > > On Sun, 10 Oct 2021 at 18:53, Korbinian Bachl > <korbinian.ba...@whiskyworld.de> wrote: > > > > Hi, > > > > we are currently using ModeShape as our JCR backend. However, as it was > > left alone by jboss (it was a jboss project) some time ago we now have the > > need to focus on some alternatives. > > Now I tried to use jackrabbit 2.20 with our app but I have the problem with > > lucene. Especially its non compatibility with itself. We also use > > Elasticsearch 7.15 and this also brings lucene with it in its > > dependencies... so 3.x and 8.x clashes and wont work. > > > > Is there any way I can let out lucene from jackrabbit to have it work? Is > > there any alternative I have for JCR usage besides removing either > > jackrabbit or elasticsearch as part of our project? > > > > I've also read about Oak but honestly didnt really understand the > > implications if it should just behave like a regular JCR2 backend. > > > > Best, > > > > KB > > > > -- > -Tor -- -Tor
