This is because Debian 12 moved to Tomcat 10 only and XWiki is not compatible with Tomcat 10 because of the javax -> jakarta package renaming.
Tomcat 10 has some automated migration if you put your application in the right folder (https://tomcat.apache.org/migration-10.html#Specification_APIs), but as advanced as this automated migration may be, I'm afraid it's whichfull thinking (it's probably working very well for a very simple application which only use the servlet API, but XWiki is using a lot of various javax which depend on each other and are not all covered by Tomcat).
A safer alternative would be The workaround is to start providing a Debian package based on use the custom XWiki Jetty based Debian package , but it's a lot more work in terms of properly making this a service in the various distributions . See XWIKI-21137. |
|
