-
Bug
-
Resolution: Won't Do
-
Major
-
3.0.0.Beta4-jboss-logging
-
None
-
None
-
Low
The logic used to select the logging provider is too fragile. It should never throw an exception while selecting a provider, because JDK logging is guaranteed to be available and should be the fallback choice. When JBoss Logging fails to select a provider, it causes deployment to fail, which violates my rule #1 of a logging framework (don't fail a build because of a failure to setup logging).
The fragile logic is the reason we get JBLOGGING-47.
- blocks
-
JBLOGGING-47 Support EAP 5.1 in JBoss Logging 3
- Resolved