On 02/02/2024 18:42, Mark Thomas wrote:
On 02/02/2024 18:19, Christopher Schultz wrote:
Mark,

On 2/2/24 10:53, Mark Thomas wrote:
The proposed Apache Tomcat migration tool for Jakarta EE 1.0.8 is now
available for voting.

The significant changes since 1.0.7 are:

- Recognize .ear files as archives

- Include .jspf and .tagf files in the conversion process

- Update dependencies

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/jakartaee-migration/v1.0.8/

The Maven staging repository is:
https://repository.apache.org/content/repositories/orgapachetomcat-1479/

The tag is:
https://github.com/apache/tomcat-jakartaee-migration/tree/1.0.8
7c1559661980d93e84b947682c67959165abbc4a

The proposed 1.0.8 release is:

[ ] -1: Broken. Do not release because...
[ ] +1: Acceptable. Go ahead and release.

+1 for stable release

Builds from source and passes the "verify" target (aka unit tests).

Running the "shaded" version of the JAR file worked on the first try with an application written using Java EE APIs and associated (legacy) libraries. A quick smoke-test in Tomcat 10.1.18 using the migrated WAR file indicates that everything is working as expected.

Details:

MacOS X Ventura x86-64
Java 21
Maven 3.8.1

Running "mvn package" results in lots of stack traces being dumped to the console, mostly java.lang.instrument.IllegalClassFormatException coming from JaCoCo and some failed unit tests.

I get warnings about weak DSA signatures for the JAR signatures. The "signed" JAR files also say they are not signed when I check with "jarsigned -verify [jar]". Is that expected if I perform the build locally?

I don't think I've tried the build with Java 21. I'm using Java 17 for that at the moment. I'll try 21 and see what happens.

I see warnings about self-signed certificates for JAR signing.

I also see the JAR is reported as unsigned. That is expected. The migration process removes the signatures.

The Jacoco plugin needed an update. I missed that in my last round of updates. I'll do that now.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to