SLF4J / SLF4J-534 [Open] Improve error handling for situations where paths is null in findPossibleStaticLoggerBinderPathSet() ============================== 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-534 ============================== 1 comment ------------------------------ Oliver Lietz on 12/Jan/22 8:52 PM This is the [calling code|https://github.com/ops4j/org.ops4j.pax.logging/blob/d3dca84d41a82a8f6bcdafdf...] in the OSGi Activator from [Pax Logging API|https://github.com/ops4j/org.ops4j.pax.logging/tree/main/pax-logging-api]: {noformat} // for each logging framework/facade supported, we'll: // 1. configure the facade/bridge/factory with single instance of PaxLoggingManager // 2. obtain the framework specific log(ger) // 3. use the log(ger) // SLF4J org.ops4j.pax.logging.slf4j.Slf4jLoggerFactory.setPaxLoggingManager(manager); org.slf4j.Logger slf4jLogger = org.slf4j.LoggerFactory.getLogger(name); slf4jLogger.info("Enabling SLF4J API support."); {noformat} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)