Re: maven-indexer / Lucene

Hi, I got it now running on my local machine (had to fight some issues with old packages in my local mvn repository). So the shaded lucene is now in the maven-indexer master, if I see it correctly. We have a dependency problem with the guava version. The selenium tests need guava 22.0 and jcr

Re: maven-indexer / Lucene

Hi So I have merged to master :-) On 18 August 2017 at 01:22, Martin Stockhammer wrote: > Hi Olivier, > > great! I will look at it. I will give you feedback the next days. > And yes I have to optimize the jcr oak part and stabilize it. I will work > on it. > > Greetings > >

Re: maven-indexer / Lucene

Hi Olivier, great! I will look at it. I will give you feedback the next days. And yes I have to optimize the jcr oak part and stabilize it. I will work on it. Greetings Martin Am 15. August 2017 11:30:04 MESZ schrieb Olivier Lamy : >Hi >Took a bit of time but I finally get

Re: maven-indexer / Lucene

Hi Took a bit of time but I finally get the branch working :-) branch: feature/jcr_oak Let me know what do you think of? Well I guess there are still some optimisations to do for jcr oak I can see some logs: 21:02:39.559 [1071] [main] WARN oak.query.QueryImpl - Traversal query (query without

Re: maven-indexer / Lucene

Hi Olivier, great! For my understanding: The dependency to lucene in the pom of indexer-core is still there, but the lucene packages are moved to the ...maven.index.shaded... package? You develop indexer-core with the standard lucene packages and the shading is executed during the build of

Re: maven-indexer / Lucene

So the repo contains a branch feature/jar_shaded_lucene here https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary and I pushed what I started for Archiva in the branch called feature/jcr_oak So in order to test it you need to build first maven-indexer from the branch

Re: maven-indexer / Lucene

We have different lucene (incompatible) dependencies that prevents us to update the maven indexer and/or jackrabbit. And this will happen again with each upgrade from one of these two packages in the future. So would be really good if we can find a solution that removes one of the lucene

Re: maven-indexer / Lucene

Can I please an obvious/stupid question? What is driving this need for change? From a quick read of the thread above, all of the options appear to introduce a lot of breaking changes, and a whole lot more uncertainty. So, what is so broken that it is driving these changes? Sent from my iPhone

Re: maven-indexer / Lucene

Yup. The idea is to have an extra jar produced by the maven-indexer with shaded lucene version. So the lucene classes (version used by Maven indexer) will be relocated in a package called org.apache.maven.index.shaded.lucene (such org.apache.maven.index.shaded.lucene.search.BooleanClause ) Then

Re: maven-indexer / Lucene

What do you mean exactly by shading? Moving to another package name? Am Mittwoch, 5. Juli 2017, 01:19:17 CEST schrieb Olivier Lamy: > maybe an option is to use some shading? > I'm thinking of shading lucene packages used by maven indexer. I can easily > provide a build for that. > WDYT? > > On

Re: maven-indexer / Lucene

maybe an option is to use some shading? I'm thinking of shading lucene packages used by maven indexer. I can easily provide a build for that. WDYT? On 26 June 2017 at 11:49, Olivier Lamy wrote: > Hi > graph/document storage could be convenient (but not possible with neo4j as

Re: maven-indexer / Lucene

Hi graph/document storage could be convenient (but not possible with neo4j as it's GPL license [1]) well we can add solr as an additional webapp with our jetty distribution but this will be a pain for users who want to use tomcat or any other servlet container... we still need to investigate a new

Re: maven-indexer / Lucene

I think we merge the branch to the master, when it's decided what way to go. Do you refer to the intermittent failures of store-jcr module with your answer or do you refer to other issues? I had the intermittent failures too and thought about some race condition, because JCR Oak is very

Re: maven-indexer / Lucene

Yes, you are right. The lucene dependency causes a lot of trouble and will cause headaches with each version change of one of the dependencies. What are the requirements for a replacement? - We want to store hierarchical data? - We want to store metadata for nodes ? - Fulltext search (only

Re: maven-indexer / Lucene

well the issue is non compatible version of Lucene for Maven Indexer and Oak (well I can try push a patch to Oak for upgrading...) On 24 June 2017 at 08:41, Olivier Lamy wrote: > Hi > Maven Indexer 6.0-SNAPSHOT doesn't need anymore plexus bridge. > I'm working on it in the

Re: maven-indexer / Lucene

Hi Maven Indexer 6.0-SNAPSHOT doesn't need anymore plexus bridge. I'm working on it in the branch ( feature/jcr_oak ) Not sure why but I have intermittent failure with store-jcr module. I definitely agree on the upgrade. Well we can simply detect it's not oak compatible and schedule a full reindex

Re: maven-indexer / Lucene

Hi, upgrading the maven indexer leads to some major changes. Lucene is used by maven-indexer and also by jackrabbit. Jackrabbit sticks to the old 3.x version and, as I see it, they will not move to a newer version. There is Jackrabbit Oak as alternative. I tried a proof of concept and could

Re: maven-indexer / Lucene

Hi, Remember jackrabbit depends on Lucene as well so upgrading Lucene can be a problem here. Regarding maven-indexer yes we can depend on a snapshot until the release. I can release it ;-) On 13 June 2017 at 06:06, Martin wrote: > Hi, > > the lucene version depends on the

maven-indexer / Lucene

Hi, the lucene version depends on the maven indexer. But I'm not sure about the current state of maven-indexer. The version has not changed since some 2013. There are commits on the master branch since then, and the lucene version has been changed too, but no releases were tagged. Does it make