Re: [PR] VELOCITY-942 - VelocityViewServlet extending from j akarta.servlet instead of javax.servlet [velocity-tools]

arkanovicz commented on PR #15:
URL: https://github.com/apache/velocity-tools/pull/15#issuecomment-2403753398

   > The API is stable, implementations are refined. I see nothing wrong with that.
   
   There is [a lot more](https://projects.eclipse.org/releases/jakarta-10) than the servlet API to migrate in a real J2E webapp (activation, mail, beans, etc.). And the dependencies are intertwined, you cannot keep the servlets API on javax- and use the remaining on jakarta-. So yes, jakarta EE *will* become the de facto standard and we should align with this fact today.
   
   If we stay on the course of two modules rather than the 3.x/4.x proposal aforementioned, it means that the javax should be the one with copied sources and a dedicated suffix, not the reverse.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]