Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
2.0.6
-
None
-
None
Description
chris created this issue on 28/Feb/23 10:41 PM
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
Require-Bundle: slf4j.api
while at the same time slf4j-api MANIFEST contains this
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?