Currently Artemis requires at least Java 11 to build and run. We moved from
Java 8 to 11 almost exactly 3 years ago in version 2.20.0 which was
released in December 2021.

I recently noticed that security fixes for Jetty 10 (which we embed) will
end in January 2025 [1]. Jetty 12 would be relatively simple to integrate
so it would be a natural solution to this problem. However, it requires
Java 17.

Java 17 was released just before we moved to 11 in 2021 and adoption has
been accelerating ever since according to this article [2]. Lots of major
open source projects have moved to 17 so we'd be in good company.

At first I was hesitant to propose this move in a minor release, but then I
realized we've already done this in both Artemis and Classic.

Assuming we agree on this proposal I plan to release 2.39.0 this month
requiring Java 17. I already have a branch with Java 17 and Jetty 12
working. It only took a couple of hours to implement.


Justin

[1] https://github.com/jetty/jetty.project/issues/10485
[2] https://newrelic.com/resources/report/2024-state-of-the-java-ecosystem

Reply via email to