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

Hi, Am Dienstag, dem 15.08.2023 um 14:52 +0200 schrieb J. Tóth Tamás: > 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

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

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

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

Hello, Am Montag, dem 07.08.2023 um 20:22 +0200 schrieb J. Tóth Tamás: > Hi, > > Did you notice my reply sent on 4 July? Yes, I did. Please keep the bug report always in CC. > We’d like to gradually upgrade > to Bookworm, but I don’t want to make sysops’ lives more complicated by > giving

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

Hi, I’ve installed the tomcat-jakartaee-migration package, but it still throws the same exception. Are you sure the JAR file it contains is on the classpath of Tomcat? Also, thinking about what I would’ve done if this package was suggested or even recommended – I probably wouldn’t have

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

Am Montag, dem 03.07.2023 um 18:28 +0200 schrieb Tamás J.Tóth: > > > The web app doesn't load. The Tomcat log contains the following: > > WARNING [main] org.apache.catalina.startup.HostConfig.migrateLegacyApp > Migration failure > java.lang.NoClassDefFoundError:

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

Package: tomcat10 Version: 10.1.10-1 Severity: important X-Debbugs-Cc: debreport...@jnet.hu Dear Maintainer, The deployment-time Java EE to Jakarta EE migration, as documented in the Tomcat 10 migration guide , fails with