mjschwaiger commented on PR #15: URL: https://github.com/apache/velocity-tools/pull/15#issuecomment-2701123026
In https://github.com/apache/velocity-tools/pull/15#issuecomment-2403206831, possible ideas/concepts for a first solution were already summarised in October last year. Unfortunately, it became a bit quiet after that. Now I wanted to ask whether there has been any further progress on this topic in the meantime and what the next steps are here. Even though I'm probably repeating a few things, my personal opinion on the subject is also that you could use the -jakarta classifier to support Jakarta 10 EE for existing projects. Other projects in the Java ecosystem, such as Hibernate, have also gone down this route. In Hibernate 5, there is also hibernate-core-jakarta in addition to hibernate-core (javax). In Hibernate 6, only hibernate-core with Jakarta 10 EE support exists and hibernate-core-jakarta is no longer available. One approach could be to switch to Jakarta by default in Velocity 4.x and additionally provide a -java module - if this is still required at that time. As already mentioned by others also in issue [VELTOOLS-202](https://issues.apache.org/jira/browse/VELTOOLS-202) it would be really be great to have a solution to support of jakarta.servlet also in Velocity. -- 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
