Am 05.12.24 um 18:14 schrieb Christopher Schultz:
The proposed Apache Tomcat 10.1.34 release is now available for
voting.
All committers and PMC members are kindly requested to provide a vote if
possible. ANY TOMCAT USER MAY VOTE, though only PMC members votes are
binding. We welcome non-committer votes or comments on release builds.
The notable changes compared to 10.1.33 are:
- Add strong ETag support for the WebDAV and default servlet, which can
be enabled by using the useStrongETags init parameter with a value set
to true. The ETag generated will be a SHA-1 checksum of the resource
content.
- Add support for RateLimit header fields for HTTP (RFC draft) in the
RateLimitFilter. Based on pull request #775 provided by Chenjp
- Update Tomcat's fork of Commons DBCP to 2.13.0.
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.34/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1525
The tag is:
https://github.com/apache/tomcat/tree/10.1.34
https://github.com/apache/tomcat/commit/
acf7da1801a4751b282a70ced24b73c1046db831
Please reply with a +1 for release or +0/-0/-1 with an explanation.
At least three test classes fail when testing with Java 11:
org.apache.catalina.valves.TestJDBCAccessLogValve
org.apache.catalina.session.TestPersistentManagerDataSourceStore
org.apache.catalina.servlets.TestWebdavPropertyStore
java.sql.SQLException: org/apache/derby/jdbc/EmbeddedDriver has been
compiled by a more recent version of the Java Runtime (class file
version 61.0), this version of the Java Runtime only recognizes class
file versions up to 55.0
It seems there was no derby update, but those classes were adjusted
recently, so likely the tests are new. There are a few other classes
using derby as well. They seem to catch the errors, because their tests
do not escalate to a test failure or error.
IMHO not critical for the release vote, but we should fix it.
Best regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
