Hi all,
As a result of the discussions and reminding myself of various issues I
intend to proceed as follows:
- Switch the minimum JRE to Java 17 for Tomcat 11. While Jakarta
EE 11 permits a minimum of Java 21, we will decide later whether to
increase the minimum Java version to 21 for Tomcat 11.
- Switch the CI systems to build with Java 17 for all branches except
Tomcat 8.5.x on buildbot since the version of ECJ we are restricted to
for Tomcat 8.5.x has issues on Java 17 (BZ 65599).
- I intend to leave the minimum build version as Java 11 for 8.5.x,
9.0.x and 10.1.x as there is no driver to increase that at this time
Mark
On 11/01/2023 11:23, Mark Thomas wrote:
Hi all,
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.
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.
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).
I don't think there are any other immediate implications for Tomcat 11.
I'll continue to track the changes in the various specifications. The
summary at the moment is:
- removal of SecurityManager references from all
- servlet
- minor improvements / new features
- lots of clarifications of the Async API
- possible new low level HTTP API but not much movement so far
- EL
- removing reference to JavaBean spec is largish piece of work
- JSP
- no plans other than necessary updates triggered by changes in
EL/Servlet
- WebSocket
- minor improvements / new features
- clarifications
Mark
[1] https://www.eclipse.org/lists/jakartaee-platform-dev/msg03898.html
---------------------------------------------------------------------
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
