The test build of Velocity Engine 2.1 RC3 is available.
No determination as to the quality ('alpha,' 'beta,' or 'GA') of
Velocity Engine 2.1 RC3 has been made, and at this time it is simply a
"test build". We welcome any comments you may have, and will take all
feedback into account if a quali
That's a good point: the name of the logger used to log deprecations
should start with "org.apache.velocity" so that it does respect the
logging hierarchy.
On 15/03/2019 09:59, Greg Huber wrote:
If I change in class org.apache.velocity.util.DeprecationAwareExtProperties
protected static Logge
For slf4j to work properly, you need to have only one slf4j binding jar
in your classpath, otherwise the results are unpredictable as to which
binding will be chosen by slf4j. So you really need to get rid of either
log4j-slf4j-impl-2.11.2.jar (which redirects slf4j logs towards log4j)
or webap
If I change in class org.apache.velocity.util.DeprecationAwareExtProperties
protected static Logger logger = LoggerFactory.getLogger("deprecation");
to
protected static Logger logger =
LoggerFactory.getLogger(DeprecationAwareExtProperties.class);
It now logs correctly:
2019-03-15 08:53:10,076 W
...logging..nightmare...I should already be logging with SLF4J, adding the
listener I now get in catalina.out and still no log messages.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/home/ghuber/git/events/events/src/main/webapp/WEB-INF/lib/log4j-slf4j-impl
