Am 03.07.23 um 21:33 schrieb Mark Thomas:
The proposed Apache Tomcat 11.0.0-M8 release is now available for
voting.
Apache Tomcat 11.0.0-M8 is a milestone release of the 11.0.x branch and
has been made to provide users with early access to the new features in
Apache Tomcat 11.0.x so that they may provide feedback. The notable
changes compared to the previous milestone include:
- Add ContextNamingInfoListener, a listener which creates context naming
information environment entries
- Add PropertiesRoleMappingListener, a listener which populates the
context's role mapping from a properties file.
- Update the Jakarta EL and Jakarta WebSocket implementations to align
with the latest changes planned for Jakarta EE 11
For full details, see the change log:
https://nightlies.apache.org/tomcat/tomcat-11.0.x/docs/changelog.html
Applications that run on Tomcat 9 and earlier will not run on Tomcat 11
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. Applications using deprecated APIs may require
further changes.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-11/v11.0.0-M8/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1441
The tag is:
https://github.com/apache/tomcat/tree/11.0.0-M8
434400d882a20e12ea03855f4bd93451bd3362c6
The proposed 11.0.0-M8 release is:
[ ] -1 Broken - do not release
[ ] +1 Alpha - go ahead and release as 11.0.0-M8
During
downloadfile:
[get] Getting:
https://repo.maven.apache.org/maven2/net/jsign/jsign/4.2/jsign-4.2.jar
[get] To:
/shared/build/autobuild/workdirs/current/20230704_112956/bld/tomcat110_incoming/deps/download-1593579538.tmp
I get
Checksum check failure for jsign-4.2.jar (.../deps/download-1593579538.tmp).
Algorithm: MD5|SHA-1
Expected value:
79c4f9bdff74a4ccee3d72f020ad45b7|5a6677625413e0d8acb52f80fa6fbb9031a6a9d0
Actual values:
SHA-512:
0a5e3a96a99b6736fed913da201c0003d2009690b4157ad9894107b1b12b5e76befd0b0f5bf016b475c71b09e97f3d1eac8c4fab138a968fa64beec527dee16d
SHA-384:
763de16603fc1921f86643e1c1103f40f5d8c82db4c6a2f90c89aa4baeabd02fd17cf35d587ff00540ffef369a57fb8e
SHA-256: 290377fc4f593256200b3ea4061b7409e8276255f449d4c6de7833faf0850cc1
SHA-1: 1e3b44e0114d599b05be243513b85a51b0c45401
MD5: 10fb38a1182515d583a1e252c8219eae
Was there some dependecy version upfdate without adjusting checksums? Or
should I look for a problem on my side?
Thanks ands regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
