Details
-
Bug
-
Resolution: Done
-
Major
-
3.2.0.Final, 3.3.0.Beta1
-
None
-
None
Description
There seems to be a typo in org.jboss.logging.LoggingProviders in the method tryLog4j(): the logging provider implementation used is Log4j2LoggerProvider, whereas it should be Log4jLoggerProvider.
The net effect is that if I have log4j jars on the classpath and include a log4j configuration, the configuration gets parsed but log4j is not used as the logging provider; instead, JDK logging provider is used.
