michael-o commented on PR #15: URL: https://github.com/apache/velocity-tools/pull/15#issuecomment-2404371621
> > I am against that. Cutting off people for the years to come for a long waited update is not right. Both Jetty and Tomcat will support javax for quite some time. > > I'm not speaking of cutting them off. I'm speaking of keeping javax- for 3.x releases and switch to jakarta- for 4.x releases. It's twice as many releases but they would be done in the same momentum. The bonus is that there is no extra module. I see, this contradicts your message here: https://github.com/apache/velocity-tools/pull/15#issuecomment-2403418376 Changing within a minor version is not OK. I am fine to move the current module in 4.x to jakarta and have a new module for `javax`. -- 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: dev-unsubscr...@velocity.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
