michael-o commented on PR #15:
URL: https://github.com/apache/velocity-tools/pull/15#issuecomment-1633095679
I can easily explain why I have immediate closed this out: Before opening a
PR for such a high-impact change I would expect a discussion in the JIRA issue
about a possible solution
[
https://issues.apache.org/jira/browse/VELTOOLS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov moved VELOCITY-942 to VELTOOLS-202:
--
Component/s: VelocityView
(was: Engine)
ppodgorsek commented on PR #15:
URL: https://github.com/apache/velocity-tools/pull/15#issuecomment-1632979410
@michael-o Can you explain why modernising Velocity to use Jakarta is a joke
for you? It's not right to expect all downstream projects to use the Tomcat
migration tool when this
ChristopherSchultz commented on PR #15:
URL: https://github.com/apache/velocity-tools/pull/15#issuecomment-1632889781
I think it's totally serious. IMO, VelocityTools needs a branch (or main) to
migrate to Jakarta EE. Not everybody is going to let their web applications
languish forever.
michael-o commented on PR #15:
URL: https://github.com/apache/velocity-tools/pull/15#issuecomment-1632855512
This can't be serious
--
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
michael-o closed pull request #15: VELOCITY-942 - VelocityViewServlet extending
from jakarta.servlet instead of javax.servlet
URL: https://github.com/apache/velocity-tools/pull/15
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
ppodgorsek opened a new pull request, #15:
URL: https://github.com/apache/velocity-tools/pull/15
(no comment)
--
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
