On Fri, 2025-01-17 at 10:52 +0100, Julian Sedding wrote: > One way to satisfy these requirements could be to > - attach a fragment bundle to the slf4j-api bundle, where the > fragment > provides an Import-Package header for ch.qos.logback.classic.spi and > a > META-INF/service/org.slf4j.spi.SLF4JServiceProvider file pointing to > ch.qos.logback.classic.spi.LogbackServiceProvider > - attach a fragment bundle to the logback-classic bundle, where the > fragment provides an Import-Package header for > org.apache.sling.commons.log.logback.spi. and a > META-INF/service/ch.qos.logback.classic.spi.Configurator file > pointing > to org.apache.sling.commons.log.logback.spi.DefaultConfigurator
My reading of [1] indicates that this could work. > A more sophisticated version could also "attach" implementations of > the respective APIs that perform an OSGi service lookup of and > delegate to a service. But maybe the above is less dynamic, which > might be good for logging. Yes, I think that in this scenario less dynamic is better. Thanks, Robert [1]: https://docs.osgi.org/specification/osgi.core/8.0.0/framework.module.html#framework.module.fragmentbundles
