SLF4J / SLF4J-561 [Open] SLF4J 1.x to 2.x migration adapter library. ==============================
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-561 ============================== 1 comment ------------------------------ Ceki Gülcü on 20/Sep/22 11:45 AM [~garretwilson] Thank for doing this. I should mention that SLF4J does take into account StaticLoggerBinder classes found on the class path for reasons of clarity. The solution to the migration is simple, the end-user places a logging backend on the classpath or the module path as appropriate for the version of slf4j-api in user. Also note that JMPS does not allow modules to occupy the same package space. Thus, we know for sure that StaticLoggerBinder will not work in a modular environment. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59) _______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/slf4j-dev
