Bug#1040226: tomcat10: deployment-time Java EE to Jakarta EE migration fails

J. Tóth Tamás debreportbug at jnet.hu
Tue Aug 15 13:52:21 BST 2023


Hi,

> Please keep the bug report always in CC.

I thought my 8 August mail contains no new information, so it makes no 
sense to spam the BTS with it. But okay, next time (and this time) I’ll 
use Reply All regardless of the message content.

>> We’d like to gradually upgrade
>> to Bookworm, but I don’t want to make sysops’ lives more complicated by
>> giving them one WAR file to install on Bookworm and another one to
>> install on Bullseye.
> 
> […] You can just manually run the tomcat-jakartaee-migration tool on
> your existing war files. All it mainly does is to replace the old
> occurrences of javax.* with jakarta.*.

That’s exactly what I meant by “making sysops’ lives more complicated by
giving them one WAR file to install on Bookworm and another one to 
install on Bullseye”, so it’s out of question for me in production.

> You could also send a patch with your proposed changes to Debian's tomcat10 > package and I take a look at it.

I created https://salsa.debian.org/java-team/tomcat10/-/merge_requests/1 
– it’s quite likely wrong in its current form, but I hope it can be fixed.

Tamás



More information about the pkg-java-maintainers mailing list