arkanovicz commented on PR #19: URL: https://github.com/apache/velocity-tools/pull/19#issuecomment-3480823005
Most of the standard containers are maintaining old versions for javax and switching to jakarta in their new versions. I think that the easiest course of action is to do the same, because there is an underneath constraint about the target JVM version, and it will avoid us the hassle of maintaining different modules on the same sources. So my plan is: - to release a 3.2 tools version on javax - to release a 4.0 tools version on jakarta with a new velocity-master targeting the jvm 11 @michael-o , in [this thread](https://github.com/apache/velocity-tools/pull/15), you said: >> There is another course of action, now that I think of it: maintain the tools 3.1.x on javax and switch on jakarta for 3.2+. > 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. But there is no reason why we cannot backport every new feature to the 3.x branch, so users wouldn't be cut off, would they? And otherwise, I don't really know how to handle the JVM target difference. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
