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
