Thorbjørn Ravn Andersen created SLF4J-433:
---------------------------------------------
Summary: slf4j backend configuration errors are not fatal
Key: SLF4J-433
URL: https://jira.qos.ch/browse/SLF4J-433
Project: SLF4J
Issue Type: Improvement
Environment: I know that a great deal of care has been put into making
slf4j invisible to the application doing the logging. This includes
configuration errors being transparent and all.
We consider logging framework configuration errors fatal, and would like a
mechanism that can tell the main application that the logging framework is
broken so it can do an emergency shutdown. Our usecase is at application
start up (first logging statement) but the generic case would probably be after
each (re)configuration.
As we by default cannot specify this through the configuration file, this
probably needs to be triggered by a system property. I'd really prefer a
solution which does not "know in application code" that the slf4j backend is
logback.
Reporter: Thorbjørn Ravn Andersen
Assignee: SLF4J developers list
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
_______________________________________________
slf4j-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/slf4j-dev
