logback / LOGBACK-1729 [Open] Add OSGi Service Loader Mediator entries to load logback Configurators ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1729 ============================== Issue created ------------------------------ Hannes Wellmann created this issue on 23/Mar/23 12:49 Summary: Add OSGi Service Loader Mediator entries to load logback Configurators Issue Type: Improvement Affects Versions: 1.3.5, 1.4.5 Assignee: Logback dev list Components: logback-classic Created: 23/Mar/23 12:49 Environment: The Manifest of logback-classic does not declared the OSGi Service Loader Mediator entries to be able to consume {{logback.classic.spi.Configurator}} services provided by other bundles. At the moment, if one provides a {{Configurator}} in another bundle this has to be workaround. For example when using Apache Aries SPI Fly by using the [Dynamic Weaving by auto properties|[https://aries.apache.org/documentation/modules/spi-fly.html#_dynamic_weaving...]], the following VM-argument needs to be added to an application: {{-Dorg.apache.aries.spifly.auto.consumers=ch.qos.logback.classic}} Furthermore the OSGi Service Loader Mediator entry for the provided {{jakarta.servlet.ServletContainerInitializer}} service (implemented by {{{}LogbackServletContainerInitializer{}}}) is missing as well. Priority: Major Reporter: Hannes Wellmann ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)