Hi, this issue is known and cannot be solved by just patching lucene, it affects the whole lucene infrastrcuture. A change on this would break almost any app out there so it needs to be done on a major release.
In addition, as Lucene uses SPI / service loaders, auto-modules don't works anyways, so you have to pack all of lucene into one module. The current recommendation is to do this on packaging. Some time in the future we will modularize Lucene, but that’s not a big priority yet. When this is done, also the plugin/service loading mechanism needs module-info.class files. Uwe ----- Uwe Schindler Achterdiek 19, D-28357 Bremen https://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Philippe Cadé <philippe.c...@gmail.com> > Sent: Thursday, September 5, 2019 2:11 PM > To: java-user@lucene.apache.org > Subject: Split package in Lucene 8.2.0 > > Dear all, > > We are working on getting rid of all split packages in our product and our > dependencies. We have included Lucene 8.2.0 and noticed that both the > lucene-core-8.2.0.jar and lucene-analyzers-common-8.2.0.jar files use the > org.apache.lucene.analysis.standard package. This is not allowed anymore > since Java 9 and it will create trouble with a modularized application. > > We are using the jsplitpkgscan project [1] to find those split packages. > > I was going to open a JIRA issue for this but JIRA tells me that I need to > ask on the mailing list first, so here you go. > > Correcting this is most likely just moving classes in distinct packages > which should not be too complex. > > Philippe > > [1] https://github.com/AdoptOpenJDK/jsplitpkgscan --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
