Mark,
On 1/11/23 06:23, Mark Thomas wrote:
The Jakarta EE platform group has announced that the minimum Java
version for Jakarta EE 11 will be Java 21. [1]
Given that the Java SecurityManager was deprecated in Java 17 and
planned for removal I intend to remove all references to the
SecurityManager from the Tomcat 11 code base. I plan to do this shortly.
+0
This will complicate back-ports, but I suppose we must do it sometime.
We would normally make Java 21 the minimum Java version. Given that Java
21 is still in EA, I don't plan to do that yet.
We could switch all branches to Java 17 as the the default build JRE now
as that supports targeting Java 7 onwards. That would allow us to easily
use some newer Java features in Tomcat 11 whilst still only requiring
RMs to use a single JDK version. If there are no objections I'll do this
shortly.
Sure.
Java 21 supports targeting Java 8 onwards which means we won't be able
to switch to that when available for all branches unless Tomcat 8.5.x
has already reached EOL.
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).
On 1/11/23 08:00, Mark Thomas wrote:
> 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)
I agree with Tim: If Jakarta EE 11 "requires" Java 21 (even if there are
no binary reasons why that is the case), then I think it's appropriate
to use that for builds and an API baseline. If we got a complaint from a
user that their application running on Tomcat 11 was failing due to some
weirdness in the application that was obviously caused by running it on
Java 11 or whatever, we'd first tell them that they must be using Java
21, per spec. There is no reason to support Tomcat 11 in a pre-Java-21
environment, so let's go ahead and use Java 21 for the whole process.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
