пт, 30 янв. 2026 г. в 12:37, Mark Thomas <[email protected]>: > > On 27/01/2026 20:23, Michael Osipov wrote: > > On 2026/01/27 17:40:11 Mark Thomas wrote: > >> Hi, > >> > >> I am expecting Tomcat 12 to be released - or get close to release - in > >> the next 12 months. Following our usual pattern, that means we'd > >> deprecate 9.0.x around the same time. > >> > >> The first 9.0.x release was November 2015 with the first stable release > >> in January 2018. > >> > >> We have previously discussed various forms of extended Tomcat 9 support > >> because it is the last Tomcat version that supports that Java EE API. > >> > >> With the above in mind, I'd like to propose the following: > >> > >> - Set EOL for 9.0.x as 31 March 2027 > >> > >> - Plan for 9.1.x releases to start in April 2027 > >> > >> - 9.1.x to different from 9.0.x in the following ways (all aligned with > >> 10.1.x): > >> - No APR support > >> - Require Tomcat Native 2.x (was 1.3.x) > >> - Minimum Java version is 11 > > > > Why raising to Java 11 if Java EE targets Java 8? > > It was to make it easier to keep the code aligned with 10.1.x (which > makes back-ports easier) but we'll be staying on Java 8.
1. I think that we will sunset 10.1.x at the same time, to have 3 versions to support: (9.x, 11, 12)? As such, it makes sense to align with 11.0.x instead? 2. I do not like having to support 9.0.x and 9.1.x at the same time. Can the same goal be achieved while staying at 9.0.x? E.g. like I see in browsers: 1) disable a feature, hiding it under an obscure option (e.g. a system property) 2) after a grace period [1] remove it entirely. [1] I think that a good grace period here may be 6 months. One we have removed those features, we can update internals to align with later versions of Tomcat. 3. I think dropping support for Tomcat Native 1.3.x (and thus removing the APR connector) is the first goal. If we go this way, We may start with raising TCN_RECOMMENDED_* values to match Tomcat Native 2.0.x. That means that using 1.3.x (and APR connector) will produce a warning. https://github.com/apache/tomcat/blob/9.0.x/java/org/apache/catalina/core/AprLifecycleListener.java#L69 4. Regarding Java 11. - If I think of people still running older (unsupported) versions of Tomcat, Tomcat 9 with Java 8 is a good stable point to upgrade from those legacy configurations. - Personally, I run Tomcat 9 with Java 11 or Java 17, but I plan to update all those to Tomcat 11. - An update to a later version of Java will allow updating ECJ bundled with Tomcat. (BTW, alternatively we may recommend to reconfigure tomcat to use the JDK compiler, as Java nowadays comes as a JDK) Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
