[jboss-jira] [JBoss JIRA] (JBLOGGING-112) JBoss Logging doesn't recognize log4j implementation

[ https://issues.jboss.org/browse/JBLOGGING-112?page=com.atlassian.jira.plu... ] Richard Achmatowicz commented on JBLOGGING-112: ----------------------------------------------- Note: when the logging implementation is chosen via org.jboss.logging.provider, if certain classes cannot be found (e.g. org.apache.log4j.LogManager), a ClassNotFoundException is raised but then swallowed and another provider is chosen. If a user specifies a specific provider but either forgets to have the provider on the classpath or chooses the wrong maven artifact, it would be nice to log the ClassNotFoundException with an appropriate warning. I spent a lot of time trying to use log4j and found that the problem was having an old enough maven artifact on the classpath which contained the LogManager, and the only easy way to find the problem was but debugging the sources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)