Re: [ANNOUNCE] Velocity Engine 2.1 RC2 test build available

2019-03-14 Thread Greg Huber
Is there any way to check if the depreciated properties logging is working? I would have thought I would see some messages in the logs: eg for my resource.loader = webapp, my 2.0: webapp.resource.loader.description=Webapp Resource Loader 2.1 property name: resource.loader.. Cheers Greg O

Re: [ANNOUNCE] Velocity Engine 2.1 RC2 test build available

2019-03-14 Thread Claude Brisson
I would say yes, since most test cases still use the deprecated properties. One of the test cases explicitly checks for the warning in the logs, which should be something like:     [warn] configuration key 'webapp.resource.loader.description' has been deprecated in favor of 'resource.loader.w

Re: [ANNOUNCE] Velocity Engine 2.1 RC2 test build available

2019-03-14 Thread Greg Huber
Tomcat logs (would be the most useful). I know the logging works because if there is an invalid #if I get a log message. On Thu, 14 Mar 2019 at 16:31, Claude Brisson wrote: > I would say yes, since most test cases still use the deprecated properties. > > One of the test cases explicitly checks

Re: [ANNOUNCE] Velocity Engine 2.1 RC2 test build available

2019-03-14 Thread Claude Brisson
Those logs are emitted quite early in the webapp initialization. So chances are the logger is initialized afterwards. If you are using the webapp-slf4j-logger to forwards slf4j logs towards tomcat, be sure to:  - use the latest version (1.4) - put this at the very beginning of your web.xml f