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 <[email protected]>: > > 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 >
