[
https://jira.qos.ch/browse/SLF4J-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ceki Gülcü reopened SLF4J-390:
------------------------------
> 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/slf4j/LoggerFactory.java#L422].
> 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/slf4j/LoggerFactory.java#L194]).
> 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)
_______________________________________________
slf4j-dev mailing list
slf4j-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-dev
