SLF4J / SLF4J-583 [Open] incorrect require-bundle in slf4j-simple to slf4j-api since 2.0.6 ============================== 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/SLF4J-583 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 17/Mar/23 8:10 Summary: incorrect require-bundle in slf4j-simple to slf4j-api since 2.0.6 Issue Type: Bug Assignee: SLF4J developers list Created: 17/Mar/23 8:10 Priority: Blocker Reporter: Ceki Gülcü Description: Since 2.0.6 the symbolic names are changed in SLF4J which introduced an inconsistency which creates a problem within OSGi environments slf4j-simple MANIFEST contains this {{}} {code:java} Require-Bundle: slf4j.api {code} while at the same time slf4j-api MANIFEST contains this {{}} {code:java} Bundle-SymbolicName: org.slf4j.api\{code} {{}} *reproduction:* download slf4j-simple and slf4j-api from mvncentral and inspect the manifest in the jars As far as I can tell at this moment it is since the maven-bundle-plugin is used which might be incorrectly configured. It is also weird that there is already a manifest.mf file in the sourcecode which does not seem to be used but overwritten by the maven-bundle-plugin as in manifest.mf files in the source the symbolic bundle names have not changed. Sidenote: all symbolic bundle names have changed which is anyhow a change which results in a lot of work in OSGi based projects as all manifest.mf files need to be adjusted. I have a feeling this was an unwanted change? ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)