SLF4J / SLF4J-586 [Open] MANIFEST.MF exports a package with a former version number ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-586 ============================== 1 comment ------------------------------ Frédéric Fays on 31/Mar/23 18:36 [~HannesWell] Thank you for your detailed analysis In fact I'm glad there has been a good fruitfull discussion on both projects. I.e. I remembered that not all is black and white, and I don't want to play the blame game, just attempting to add my inputs to the reflection. My mistake came from my assumption that an OSGi bundle can only provide packages from its own project. Since, I've learned that is it acceptable to re-bundle packages from other projects for convenience. So in issue [https://github.com/ops4j/org.ops4j.pax.logging/issues/519] discussion, the team explain why decision to packages from all facades of other logging API has been made. I still believe such choice makes the troubleshooting harder; On the other hand there is nothing in the OSGi specification ruling against it, so they made an acceptable pragmatic choice. In issue [https://github.com/ops4j/org.ops4j.pax.logging/issues/518] they emphasize there is the "provider=paxlogging" parameter in the Export-Package directive to enforce the OSGi system bundle to wire the package with pax-logging-api bundle. And for this issue, it is a project team choice as well. For which I still believe such choice makes the troubleshooting harder... I.e. If SLF4J users wants to adopt the version 2, they have to go for it and update their MANIFESTS (this is my opinion). Still if you think providing a backward compatibly for early adoption of SLF4j library is a good trade-off, it is your choice! And nothing in the OSGi specification ruling against it. So if your decision to {{Export-Package: org.slf4j;version="1.7.36"}} is final then please close this ticket. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)