[ https://jira.qos.ch/browse/SLF4J-390?page=com.atlassian.jira.plugin.system.i... ] Ceki Gülcü commented on SLF4J-390: ---------------------------------- After thinking about this problem quite a bit, I feel that changing more code in org.slf4j.LoggerFactory to accommodate this particular case would do more harm than good.

FAILED_INITIALIZATION case in LoggerFactory.getILoggerFactory swallows root exception -------------------------------------------------------------------------------------

Key: SLF4J-390 URL: https://jira.qos.ch/browse/SLF4J-390 Project: SLF4J Issue Type: Bug Affects Versions: 1.7.22 Reporter: Andreas Sewe Assignee: Ceki Gülcü Priority: Minor Fix For: 1.7.24

I have a hard time triaging an {{IllegalStateException}} thrown by {{LoggerFactory.getILoggerFactory}} that has been reported by a user ([Eclipse Bug 510487|https://bugs.eclipse.org/bugs/show_bug.cgi?id=510487]) as the root exception is not wrapped by the {{IllegalStateException}}: [https://github.com/qos-ch/slf4j/blob/v_1.7.22/slf4j-api/src/main/java/org/sl...]. AFAICT, that exception is only logged to the console ([https://github.com/qos-ch/slf4j/blob/v_1.7.22/slf4j-api/src/main/java/org/sl...]). This makes error reports sent by an automatic error reporting system (like the one employed for the Eclipse IDE) less useful, as the crucial information won't be included automatically. Hence, it would be great if SLF4J could hold onto the {{Throwable}} for a bit and than wrap it in the final {{IllegalStateException}}.

-- This message was sent by Atlassian JIRA (v7.3.1#73012)