Hi, First of all an update.
I have a first pass of the javax.* -> jakarta.* migration tool implemented. I have used it to convert the JSTL JARs used by Tomcat's example web application and by the unit tests. The unit tests now all pass. I have updated my "jakarta" branch [1] to include these changes. I think it is time to start work on Tomcat 10. This proposed plan should be read with the Jakarta EE Release Numbering plan [2]. 1. Create a 9.0.x branch from master. 2. Apply the commits in my "jakarta" branch to master. 3. Proceed with the various API changes, clean-ups, etc. listed in TOMCAT-NEXT.txt in the root of the repository 4. Remove all the deprecated code planned for removal in Tomcat 10. 5. Version numbering updates. 5. Produce a Tomcat 10.0.0.M1 release ASAP (best guess is mid-Jan to mid-Feb for this) 6. Announce EOL for Tomcat 7.0.x as 31 March 2021 (too soon?) The continue with monthly 10.0.0.Mx, 9.0.x and 8.5.x releases until Jakarta EE 9 is released and 10.0.0.Mx passes the TCKs. My current thinking is to start on this in January. On a related point, where so we think the javax -> jakarta migration tool should live in source control? My current thinking is that, since this is a stand-along tool it should live in a separate Git repo and have a separate release cycle (it is fairly small). If we wanted to integrate this into Tomcat's deployment process, I imagine we'd add the JAR file to the build process as a dependency like any other. Thoughts? Mark [1] https://github.com/markt-asf/tomcat/tree/jakarta [2] https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+Release+Numbering --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
