Show stacktrace for flawed discovery in diagnostic messages
-----------------------------------------------------------
Key: LOGGING-138
URL: https://issues.apache.org/jira/browse/LOGGING-138
Project: Commons Logging
Issue Type: Improvement
Affects Versions: 1.1.1, 1.1.0
Reporter: Luke Lu
It looks like since 1.1, if a custom log appender throws an exception the stack
trace is not shown in diagnostic messages, making it harder (than 1.0.4) to
find out the root cause of the log initialization problem.
Here is a simple patch against the trunk to address the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
