logback / LOGBACK-1736 [Open] Make OSGi service-loader requirement for spi.Configurator optional
============================== 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-1736 ============================== Issue created ------------------------------ Hannes Wellmann created this issue on 25/Apr/23 18:02 Summary: Make OSGi service-loader requirement for spi.Configurator optional Issue Type: Sub-task Affects Versions: 1.3.7, 1.4.7 Assignee: Logback dev list Components: logback-classic Created: 25/Apr/23 18:02 Priority: Critical Reporter: Hannes Wellmann Description: For LOGBACK-1729 the OSGi Service Loader Mediator Manifest entries were enhanced to be able to load logback {{Configurator}} services provided by other OSGi bundles. Unintentionally this requirement was only specified with {{cardinality:=multiple}} and without {{{}resolution:=optional{}}}, which means that at least one bundle providing a {{Configurator}} service is required (but multiple are possible). But having no provided {{Configurator}} at all is also a valid scenario and the code is prepared for that. Therefore the corresponding Service Loader Mediator requirement should be marked as optional ({{{}resolution:=optional{}}}) in order to allow zero up to arbitrary many provided {{Configurator}} services{{{}.{}}} ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af) _______________________________________________ logback-dev mailing list logback-dev@qos.ch https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
