Am 20.11.2026 um 05:42 schrieb Pedro F. Giffuni via dev:
  FWIW, I looked briefly at CLucene:
     https://clucene.sourceforge.net/
It uses CMake, and while the core, which is what matters to us, is dual 
Apache/LGPL, the contrib has GPL.
If it's up to voting, I think I prefer Java Lucene 8.
Pedro.
cLucene seems not well maintained.
we could switch to SQLliteFTS5 if we want to add SQLlite as an internal db that would a good fit.

Another option could be Lucene++ which has the same AL2 / GPL dual license model.

apache lucene would be my choice for now.

     On Monday, October 26, 2026 at 10:32:52 PM GMT-5, Jim Jagielski 
<[email protected]> wrote:
I've created a branch with the Lucene8 work I did, if we want to start with that:

     https://github.com/apache/openoffice/tree/lucene-8-upgrade


On Oct 26, 2026, at 12:44 PM, Pedro F. Giffuni via dev 
<[email protected]> wrote:

Hmm .. the move to Win64, and the fact that very old JVM will not be available 
anymore will inevitably mean that extensions will have to be regenerated, so my 
guess is the sooner the change, the better.
But the choice are not nice: Lucene8 is also deprecated, current release is 
10.x.
FWIW, libreoffice moved to a hacked up C version of older Lucene.
Pedro.
     On Monday, October 26, 2026 at 09:36:06 AM GMT-5, Jim Jagielski 
<[email protected]> wrote:

I remember looking into this... the issue was, iirc, something about Lucene8 
not being able to read Lucene2 indexes which are used when we install 
extensions. For a 4.2.x build that was an issue, but maybe no longer for a 
5.0.x release.


On Oct 26, 2026, at 10:26 AM, Pedro F. Giffuni via dev 
<[email protected]> wrote:
Nothing I am planning, but we are carrying obsolete Lucene 2.9.4.
The last Apache Lucene version that works with Java 8 is 8.11.4, which was 
released in September 2024.

Pedro.

--
Jim
   "This is an outrage!"
                         Tony Harrison


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to