[jira] [Commented] (VELTOOLS-202) VelocityViewServlet extending from jakarta.servlet instead of javax.servlet
[ https://issues.apache.org/jira/browse/VELTOOLS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804806#comment-17804806 ] Gernot Hueller commented on VELTOOLS-202: - [~michael-o] Yes that's what I also wrote in a mail to [dev@velocity.apache.org|mailto:dev@velocity.apache.org] to spawn a discussion - but the mail is in limbo for hours, not visible on lists.apache.org and also not rejected (I did not get an error mail) > VelocityViewServlet extending from jakarta.servlet instead of javax.servlet > --- > > Key: VELTOOLS-202 > URL: https://issues.apache.org/jira/browse/VELTOOLS-202 > Project: Velocity Tools > Issue Type: New Feature > Components: VelocityView >Reporter: David Ruiz de Azua >Priority: Trivial > > To whom may concern, > Currently VelocityViewServlet extends from javax rather than jakarta. > Due the cutover from Java to Jakarta, *is there any plan to make Apache > Velocity compatible with Servlet 5.0?* > Not sure if there are any plans to make the transition to Jakarta namespace > and if there is any ETA for it. > [https://jakarta.ee/specifications/servlet/5.0/apidocs/jakarta/servlet/http/httpservlet] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
[jira] [Commented] (VELTOOLS-202) VelocityViewServlet extending from jakarta.servlet instead of javax.servlet
[ https://issues.apache.org/jira/browse/VELTOOLS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804718#comment-17804718 ] Gernot Hueller commented on VELTOOLS-202: - The velocity team treatment of the servlet API change is ridiculous. I see that the work HAS already been done but the pull request has been "closed". So it means that Velocity-tools wants to stay on an old API (was outdated october 2020) forever. So I will need to either clone the code and fix it myself. Or find a template engine that is not stuck in time. > VelocityViewServlet extending from jakarta.servlet instead of javax.servlet > --- > > Key: VELTOOLS-202 > URL: https://issues.apache.org/jira/browse/VELTOOLS-202 > Project: Velocity Tools > Issue Type: New Feature > Components: VelocityView >Reporter: David Ruiz de Azua >Priority: Trivial > > To whom may concern, > Currently VelocityViewServlet extends from javax rather than jakarta. > Due the cutover from Java to Jakarta, *is there any plan to make Apache > Velocity compatible with Servlet 5.0?* > Not sure if there are any plans to make the transition to Jakarta namespace > and if there is any ETA for it. > [https://jakarta.ee/specifications/servlet/5.0/apidocs/jakarta/servlet/http/httpservlet] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
[jira] [Created] (VELTOOLS-200) current Velocity Tools use deprecated Velocity properties
Gernot Hueller created VELTOOLS-200:
---
Summary: current Velocity Tools use deprecated Velocity properties
Key: VELTOOLS-200
URL: https://issues.apache.org/jira/browse/VELTOOLS-200
Project: Velocity Tools
Issue Type: Bug
Components: VelocityView
Affects Versions: 3.1
Reporter: Gernot Hueller
when using current Velocity with current Velocity Tools View , I get the
following error messages in the log:
{{org.apache.velocity.deprecation - configuration key 'resource.loader' has
been deprecated in favor of 'resource.loaders'}}
{{org.apache.velocity.deprecation - configuration key
'webapp.resource.loader.class' has been deprecated in favor of
'resource.loader.webapp.class'}}
{{org.apache.velocity.deprecation - configuration key
'string.resource.loader.class' has been deprecated in favor of
'resource.loader.string.class'}}
{{org.apache.velocity.deprecation - configuration key
'runtime.introspector.uberspect' has been deprecated in favor of
'introspector.uberspect.class'}}
OK so maybe the old property names are used to be compatible to old Velocity
Engine versions, but the default is that we use current versions - so a
"compatibility mode" should be made smarter than just continuing to use
deprecated properties.
my gradle includes:
{{earlib group: 'org.apache.velocity', name: 'velocity-engine-core', version:
'2.3'}}
{{earlib group: 'org.apache.velocity.tools', name: 'velocity-tools-view',
version: '3.1'}}
This has also been mentioned in a recent stackoverflow thread
https://stackoverflow.com/questions/73026164/velocity-warnings-about-deprecated-keys-that-i-dont-even-use
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
