Affects Version/s: 1.1.0, 1.1.1
Fix Version/s: 1.1.2
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.
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||1.1.2 [ 12314498 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|