-
Feature Request
-
Resolution: Done
-
Minor
-
3.0.0.Beta4-jboss-logging
-
None
-
None
-
Low
Currently, JBoss Logging uses a classloading approach to look for a logging provider based on a hardcoded order of precedence. While this is sufficient for the default case, there should be a way to specify the logger explicitly, in the case that there is more than one concrete logging implementation on the classpath.
The override should be part of the API, though a system property could also be supported. The API would take precedence.
- is related to
-
JBLOGGING-47 Support EAP 5.1 in JBoss Logging 3
- Resolved