On 11/01/2023 11:49, Romain Manni-Bucau wrote:
Hi,
As an user we are adopting Tomcat 11 (even if still "on the edge") with
Java 17 (in particular for some lib/stacks) and the more reactive servlet
6.1 is very interesting so hope it can be made Java 17 compliant until
technically blocked.
Chatting with the Spring folks at $dayjob, they expressed the view that
Java 17 was likely to be the baseline for corporate users for a long
time to come.
At the moment, I see the drivers for Java 21 as:
- use new APIs (applications can do this even if the minimum version
supported is lower)
- non-preview versions of Panama and Loom (if available)
Are there are other API changes introduced between Java 17 and Java 21
that we would want to make use of?
JreCompat has a Java 19 instance but that is just controlling whether or
not to work around a bug.
Given the plan was to switch to Java 17 for building shortly and Java 21
later we don't need to make a final decision now (although gathering
views and data now is a good thing). We could switch the minimum version
for Tomcat 11 to Java 17 now and wait and see for Java 21. We'd have
from when Java 21 is released to when Tomcat 11 is declared stable to
decide whether to move the Java 21 as the minimum version.
Mark
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le mer. 11 janv. 2023 à 12:44, Mark Thomas <ma...@apache.org> a écrit :
On 11/01/2023 11:38, Rémy Maucherat wrote:
On Wed, Jan 11, 2023 at 12:23 PM Mark Thomas <ma...@apache.org> wrote:
<snip/>
The target date for Jakarta EE 11 is Q1 2024. Given that there are no
Java 21 features we want to use in Tomcat 11 right now I suggest we wait
until we need to build Tomcat 11 with Java 21 to decide what to do.
Worst case, we'll need to build most branches with Java 21 and 8.5.x
with Java 17 until 8.5.x reaches EOL (31 March 2024).
If Java 21 is the baseline, I would like to propose to drop
tomcat-native from Tomcat 11 and replace it with Panama. This is of
course assuming Panama is non preview in 21, and this also needs to
wait for some time (probably until June).
Just playing devils advocate for a second, is Java 21 going to be too
big a leap for the majority of users? Might the Tomcat community be
better with Java 17 as the minimum version for Tomcat 11?
Personally, I am in favour of Java 21 for Tomcat 11. There is always
Tomcat 10.1x for those that don't want to / can't move to Java 21. But I
did at least want to ask the question in case my views are in the minority.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
