SLF4J / SLF4J-544 [Resolved] LoggerFactory only loads services from context class loader
============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-544 ============================== 1 comment ------------------------------ Ceki Gülcü on 14/Nov/22 6:56 PM [~ichttt] [~benarnold] Thank you for you feedback. SLF4J was created to solve the classloading problems encountered with Jakarta Commons Logging and its dynamic discovery mechanism. Hence the purposefully dumb static binding mechanism that prevailed in SLF4J version 1.7.x and earlier. The current discovery mechanism which uses the thread context class loader is a involuntary mistake. It will be reverted to the behavior you suggest, that is, using the loader that loaded LoggerFactory. A more flexible loading mechanism may follow in future releases... ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59) _______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch https://mailman.qos.ch/cgi-bin/mailman/listinfo/slf4j-dev