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
