On Sat, Jul 23, 2022 at 6:08 AM Andrus Adamchik <aadamc...@gmail.com> wrote: > Hi folks,
Hello, Andrus and the dev Tapestry mailing list membeers! > As you probably know, JavaEE has been EOL'd for some time, and everyone is > slowly moving to JakartaEE. And this requires an entirely new build of every > application and framework because of the package change from "javax.*" to > "jakarta.*". > > So are there any plans to create a JakartaEE-compatible version of Tapestry > (either next to or instead of JavaEE) ? Thanks for raising this issue. We indeed need to think of a solution. Yes, any breaking changes, including Servlet API version ones, need to be done in a major release version. Backward compatibility is something very, very important to the Tapestry project for historical reasons. Regarding a jump to Servlet API 5/JakartaEE: doing that in a new Tapestry major version and backporting security fixes and occasionally other important stuff to 5.8 is definitely a correct solution for that. On the other hand, keeping 2 major versions active and having releases for both is a burden, and many people and companies are slow to adopt new versions of their servlet containers/servers, so they would miss any new features to be added in the future. So I have another possible solution in mind: finding (and if it doesn't work, write one) tool to make a copy of the source code of the subprojects that actually have Servlet API dependencies, change "javax.servlet.*" to "jakarta.servlet.*" and build them with a Maven "jakarta-ee" classifier. In addition, having the current code work with Jakarta EE/latest Servlet API version (mostly by adding default methods to deal with methods added to interfaces) This way, those ready to jump to Jakarta EE can do so without the need of Tapestry to keep 2 different branches. Regarding the tool, if we can get a list of the original (non-Jakarta-EE) and new class names (Jakarta EE), we can use the Tapestry 5.7.0 migration tool which implements exactly what we need. Thoughts? > > FWIW, in the Bootique project we decided to keep both JavaEE and Jakarta > options for at least the next major release. E.g. > https://github.com/bootique/bootique-jetty > <https://github.com/bootique/bootique-jetty> . But with every passing month, > I am less inclined to keep supporting JavaEE :) > > Andrus -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
