On 07/05/2019 08:05, Rémy Maucherat wrote: > 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 ?
I think it is good we are thinking about options but too early to settle on any one solution. The solution we adopt is going to be largely dependent on what the API projects at Eclipse decide to do. Rather than announcing a solution, how about we announce that we will continue to support the javax.* APIS (Servlet 4.0, JSP 2.3, EL 3.0, WebSocket 1.1 and JASPIC 1.1) until at least 31 Dec 2030*. Note: that means supporting all the older versions of those specs as well. Exactly how we do that is TBD. Extending Tomcat 9 support to the end of 2030 is just one possible option. Mark * Insert date of choice here. I picked first Tomcat 9 release + 10 years for typical support period + 5 years extension and rounded to the end of the year. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
