Hi, Background information: https://eclipse-foundation.blog/2019/05/03/jakarta-ee-java-trademarks/
So this is obviously a large breaking change. While there are plenty of options, there is a simple one too: - Maintain a Tomcat 9.x "forever" with Servlet 4.0. As a result, all the APIs in Tomcat 9 can remain javax.* and users with "old" applications will still have an up to date fully compatible container for them. - Have a Tomcat 10 with all API packages renamed to jakarta.*, which would provide a container for users who want to move to the new "incompatible" Jakarta specifications. This way, there's an appropriate container for everyone. Mark Struberg proposed more elaborate strategies using classloader tricks on the ASF members list, but I'm not sure this is even needed for Tomcat. Overall, the impact for Tomcat seems rather minimal given the maturity of Tomcat and its expected support lifecycle for 9.x. Comments ? Rémy
