On Thu, Apr 11, 2024 at 7:22 PM Rainer Jung <rainer.j...@kippdata.de> wrote: > > Am 10.04.24 um 20:51 schrieb Christopher Schultz: > > The proposed Apache Tomcat 10.1.22 release is now available for > > voting. Apache Tomcat 10.1.21 was canceled due to a release-build > > mistake. There are no source-level changes between 10.1.21 and 10.1.22. > > > > The notable changes compared to 10.1.20 are: > > > > - Add OpenSSL support when FFM is available > > > > - Improve locking strategies in Catalina core > > > > - Updates to Apache Commons dependencies > > > > For full details, see the change log: > > https://nightlies.apache.org/tomcat/tomcat-10.1.x/docs/changelog.html > > > > Applications that run on Tomcat 9 and earlier will not run on Tomcat 10 > > without changes. Java EE applications designed for Tomcat 9 and earlier > > may be placed in the $CATALINA_BASE/webapps-javaee directory and Tomcat > > will automatically convert them to Jakarta EE and copy them to the > > webapps directory. > > > > It can be obtained from: > > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-10/v10.1.22/ > > > > The Maven staging repo is: > > https://repository.apache.org/content/repositories/orgapachetomcat-1491 > > > > The tag is: > > https://github.com/apache/tomcat/tree/10.1.22 > > fd9c0bb1f0a7e586daabfda625ef50827bcfddf3 > > > > Please reply with a +1 for release or -0/-1 with an explanation. > > > > The proposed 10.1.22 release is: > > [X] Broken - do not release > > [ ] Stable - go ahead and release as 10.1.22 > > Unfortunately it seems broken. > > Commit 6550e203a8119683f38c182cbfbb9b56587c54a0 introduced the use of > --enable-native-access to the catalina script, which I think breaks 10.1 > on Java 11, since the flag was introduced later.
It is trivial to address by a user though. Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
