You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@opennlp.apache.org by Richard Zowalla <rz...@apache.org> on 2026/03/02 19:44:19 UTC

[DISCUSS] Move 3.x to Java 21

Hi all,

We have an open issue that may be relevant for 3.0.0-M2:
https://issues.apache.org/jira/browse/OPENNLP-1735 (Java 21)

Martin and I discussed this offline. While I personally favor keeping
Java 17 as the baseline (since I am a EE folk and EE11 is still Java 17
baseline), I understand the concerns: more and more tools are moving
toward Java 21 (recently checkstyle), and we may want to stay aligned
with that ecosystem and potentially take advantage of the latest
language features available in Java 21.

Although we could use multi-release JARs to leverage newer bytecode
versions, this would likely add some complexity to our build process.

For that reason, I’d like to start a discussion on whether we should
move to Java 21 for the 3.x release line and drop Java 17 support.

Copying users@ for information. Feel free to provide your opinion.

What do you think?

Gruß
Richard

Re: [DISCUSS] Move 3.x to Java 21

Posted by David Sanderson <da...@pathcom.com>.
In principle this upgrade to Java 21 makes sense.

However, the move to Java 21 would have the most impact on commercial 
installations that  will require expensive programming tweaks and 
regression testing to assure their customers of functional consistency 
from one upgrade to the next. Do you have any idea how large this 
segment is?

This change would have less impact private developers and hobbyists who 
are by nature more nimble and are less concerned with costs.

D. Sanderson

On 3/2/2026 2:44 PM, Richard Zowalla wrote:
> Hi all,
>
> We have an open issue that may be relevant for 3.0.0-M2:
> https://issues.apache.org/jira/browse/OPENNLP-1735 (Java 21)
>
> Martin and I discussed this offline. While I personally favor keeping
> Java 17 as the baseline (since I am a EE folk and EE11 is still Java 17
> baseline), I understand the concerns: more and more tools are moving
> toward Java 21 (recently checkstyle), and we may want to stay aligned
> with that ecosystem and potentially take advantage of the latest
> language features available in Java 21.
>
> Although we could use multi-release JARs to leverage newer bytecode
> versions, this would likely add some complexity to our build process.
>
> For that reason, I’d like to start a discussion on whether we should
> move to Java 21 for the 3.x release line and drop Java 17 support.
>
> Copying users@ for information. Feel free to provide your opinion.
>
> What do you think?
>
> Gruß
> Richard
>
-- 
Best regards,

<b><i>David Sanderson</i></b>


-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com

Re: [DISCUSS] Move 3.x to Java 21

Posted by Martin Wiesner <ma...@apache.org>.
Given that OpenNLP 2.x (J17) might maintained and around for some more months (n = ~6 once 3.x is out?), Tika has an option to get a compatible, yet update release.

As mentioned by Jeff, other ASF projects such as Lucene and Solr went forward already.

In view of the opinions and feedback received (2x +1, 1x +0, zero negative comments), and given that we don’t have a (real) show stopper / blocker, 
I’d like to conclude we have a consensus to migrate OpenNLP 3.x (*main*) to a baseline of Java 21.

Let’s move on towards 3.0.0-M2.

Best
Martin | mawiesne

> Am 05.03.2026 um 14:28 schrieb Jeff Zemerick <jz...@apache.org>:
> 
> I'm +1 as long as we don't "out run" projects that depend on OpenNLP.
> I think Lucene 10 requires Java 21, and Solr 10 will also require Java
> 21. I believe Tika is still on Java 17...? Are there any other notable
> projects we should consider?
> 
> Thanks,
> Jeff
> 
> On Thu, Mar 5, 2026 at 1:25 AM Martin Wiesner <ma...@apache.org> wrote:
>> 
>> Hi all,
>> 
>> I’m +1 for Java 21 and getting the new language features into the OpenNLP 3.x release line on our main branch.
>> 
>> For OpenNLP 2.x, I’m fine if we stick with Java 17 for users that depend on that.
>> 
>> Best
>> Martin | mawiesne
>> 
>>> Am 02.03.2026 um 20:46 schrieb Richard Zowalla <rz...@apache.org>:
>>> 
>>> I am +0 for Java 21
>>> 
>>> Am Montag, dem 02.03.2026 um 20:44 +0100 schrieb Richard Zowalla:
>>>> Hi all,
>>>> 
>>>> We have an open issue that may be relevant for 3.0.0-M2:
>>>> https://issues.apache.org/jira/browse/OPENNLP-1735 (Java 21)
>>>> 
>>>> Martin and I discussed this offline. While I personally favor keeping
>>>> Java 17 as the baseline (since I am a EE folk and EE11 is still Java
>>>> 17
>>>> baseline), I understand the concerns: more and more tools are moving
>>>> toward Java 21 (recently checkstyle), and we may want to stay aligned
>>>> with that ecosystem and potentially take advantage of the latest
>>>> language features available in Java 21.
>>>> 
>>>> Although we could use multi-release JARs to leverage newer bytecode
>>>> versions, this would likely add some complexity to our build process.
>>>> 
>>>> For that reason, I’d like to start a discussion on whether we should
>>>> move to Java 21 for the 3.x release line and drop Java 17 support.
>>>> 
>>>> Copying users@ for information. Feel free to provide your opinion.
>>>> 
>>>> What do you think?
>>>> 
>>>> Gruß
>>>> Richard
>>> 
>> 


Re: [DISCUSS] Move 3.x to Java 21

Posted by Jeff Zemerick <jz...@apache.org>.
I'm +1 as long as we don't "out run" projects that depend on OpenNLP.
I think Lucene 10 requires Java 21, and Solr 10 will also require Java
21. I believe Tika is still on Java 17...? Are there any other notable
projects we should consider?

Thanks,
Jeff

On Thu, Mar 5, 2026 at 1:25 AM Martin Wiesner <ma...@apache.org> wrote:
>
> Hi all,
>
> I’m +1 for Java 21 and getting the new language features into the OpenNLP 3.x release line on our main branch.
>
> For OpenNLP 2.x, I’m fine if we stick with Java 17 for users that depend on that.
>
> Best
> Martin | mawiesne
>
> > Am 02.03.2026 um 20:46 schrieb Richard Zowalla <rz...@apache.org>:
> >
> > I am +0 for Java 21
> >
> > Am Montag, dem 02.03.2026 um 20:44 +0100 schrieb Richard Zowalla:
> >> Hi all,
> >>
> >> We have an open issue that may be relevant for 3.0.0-M2:
> >> https://issues.apache.org/jira/browse/OPENNLP-1735 (Java 21)
> >>
> >> Martin and I discussed this offline. While I personally favor keeping
> >> Java 17 as the baseline (since I am a EE folk and EE11 is still Java
> >> 17
> >> baseline), I understand the concerns: more and more tools are moving
> >> toward Java 21 (recently checkstyle), and we may want to stay aligned
> >> with that ecosystem and potentially take advantage of the latest
> >> language features available in Java 21.
> >>
> >> Although we could use multi-release JARs to leverage newer bytecode
> >> versions, this would likely add some complexity to our build process.
> >>
> >> For that reason, I’d like to start a discussion on whether we should
> >> move to Java 21 for the 3.x release line and drop Java 17 support.
> >>
> >> Copying users@ for information. Feel free to provide your opinion.
> >>
> >> What do you think?
> >>
> >> Gruß
> >> Richard
> >
>

Re: [DISCUSS] Move 3.x to Java 21

Posted by Martin Wiesner <ma...@apache.org>.
Hi all,

I’m +1 for Java 21 and getting the new language features into the OpenNLP 3.x release line on our main branch.

For OpenNLP 2.x, I’m fine if we stick with Java 17 for users that depend on that.

Best
Martin | mawiesne

> Am 02.03.2026 um 20:46 schrieb Richard Zowalla <rz...@apache.org>:
> 
> I am +0 for Java 21
> 
> Am Montag, dem 02.03.2026 um 20:44 +0100 schrieb Richard Zowalla:
>> Hi all,
>> 
>> We have an open issue that may be relevant for 3.0.0-M2:
>> https://issues.apache.org/jira/browse/OPENNLP-1735 (Java 21)
>> 
>> Martin and I discussed this offline. While I personally favor keeping
>> Java 17 as the baseline (since I am a EE folk and EE11 is still Java
>> 17
>> baseline), I understand the concerns: more and more tools are moving
>> toward Java 21 (recently checkstyle), and we may want to stay aligned
>> with that ecosystem and potentially take advantage of the latest
>> language features available in Java 21.
>> 
>> Although we could use multi-release JARs to leverage newer bytecode
>> versions, this would likely add some complexity to our build process.
>> 
>> For that reason, I’d like to start a discussion on whether we should
>> move to Java 21 for the 3.x release line and drop Java 17 support.
>> 
>> Copying users@ for information. Feel free to provide your opinion.
>> 
>> What do you think?
>> 
>> Gruß
>> Richard
> 


Re: [DISCUSS] Move 3.x to Java 21

Posted by Richard Zowalla <rz...@apache.org>.
I am +0 for Java 21

Am Montag, dem 02.03.2026 um 20:44 +0100 schrieb Richard Zowalla:
> Hi all,
> 
> We have an open issue that may be relevant for 3.0.0-M2:
> https://issues.apache.org/jira/browse/OPENNLP-1735 (Java 21)
> 
> Martin and I discussed this offline. While I personally favor keeping
> Java 17 as the baseline (since I am a EE folk and EE11 is still Java
> 17
> baseline), I understand the concerns: more and more tools are moving
> toward Java 21 (recently checkstyle), and we may want to stay aligned
> with that ecosystem and potentially take advantage of the latest
> language features available in Java 21.
> 
> Although we could use multi-release JARs to leverage newer bytecode
> versions, this would likely add some complexity to our build process.
> 
> For that reason, I’d like to start a discussion on whether we should
> move to Java 21 for the 3.x release line and drop Java 17 support.
> 
> Copying users@ for information. Feel free to provide your opinion.
> 
> What do you think?
> 
> Gruß
> Richard