Am 01.10.26 um 12:15 schrieb Mark Thomas:
The proposed Apache Tomcat migration tool for Jakarta EE 1.0.13 is now
available for voting.
The significant changes since 1.0.12 are:
- Reduced buffering in streaming mode
- Improved handling of manifest files
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/jakartaee-migration/v1.0.13/
The Maven staging repository is:
https://repository.apache.org/content/repositories/orgapachetomcat-1607/
The tag is:
https://github.com/apache/tomcat-jakartaee-migration/tree/1.0.13
b5ef6b6c0e97d0215c5a0de822657a05fb550076
The proposed 1.0.13 release is:
[ ] -1: Broken. Do not release because...
[X] +1: Acceptable. Go ahead and release.
+1 to release
Build with JDK 25.0.4.1
Build is reproducible.
Signatures and hashes checked.
Minor observations:
- maybe we should add the new files AGENTS.md and SECURITY.md to the
source distribution; what about adding them to the binary distribution?
- not so sure about adding .gitignore to the source distribution
- even less about adding .asf.yaml to the source distribution
- if build reproducibility is not expected independent of JVM version
used to build, would it make sense to record the JVM build version
somewhere in the distributed files?
- probably tricky with maven, but it would be nice if the end of the
build procedure would result in a tree, that reflects the download tree
1:1. Currently the source and binary artefacts reside together in the
target directory. That makes comparing with the download a bit more fragile.
Thanks for RM and best regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
