First, thanks for the 5.8.4 release! The timing was perfect since
underscore.js was one of the items flagged in a recent vulnerability scan.
I am also very interested in the Jakarata EE migration. We are currently
in the process of upgrading to Spring Boot 3.2 since support for 2.7
ended in November 2023.
Given there is no schedule for official Tapestry Jakarta EE support, we
decided to create and host an internal build of Tapestry. I applied the
changes provided by Christian Köberl in pull request TAP5-2741 to the
5.8.4 sources and everything is looking good so far. Thank you so much
for providing the pull request!
We initially considered publishing the Tapestry jars with a classifier
of "jakarta" similar to other projects, but that required substantial
changes to the build. Instead, we made a few small changes to the build
to publish the Tapestry artifacts with a Maven group Id of
*org.apache.tapestry-jakarta*. That approach was much simpler and avoids
the collision with the non-jakarta artifacts.
I would be very interested in everyone's thoughts on how the official
Jakarta EE support should work. Perhaps it would be feasible to create
an automated patch and build process that can be maintained in parallel
to the official Tapestry build? While it may not be as elegant as a
fully integrated approach, I believe it would address the immediate need
for Jakarta EE artifacts without significantly increasing the
maintenance costs. Thoughts?
Best Regards,
David Taylor
On 2/13/2024 8:00 AM, Thiago H. de Paula Figueiredo wrote:
On Tue, Feb 13, 2024 at 8:20 AM Carlos Montero Canabal
<carlosmonterocana...@gmail.com> wrote:
Good job Tapestry Team, congratulations!
Thanks!
I have a question. This release supports Java 21 but checking Tomcat
versions (https://tomcat.apache.org/whichversion.html), If I want to use
Java 21 I have to use Tomcat 11.0.X and this version requires servlet spec
6.1. From the 6.0 version, servlet is provided by jakarta and all package
names switch from javax.servlet to jakarta.servlet.
Any updates about migrating tapestry code from javax to jakarta?
We won't provide any schedule, but indeed our main priority now is to
provide a Tapestry version using the jakarta.* packages and Servlet
API 6.
Cheers!
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail:users-unsubscr...@tapestry.apache.org
For additional commands, e-mail:users-h...@tapestry.apache.org
