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 ------------------------------ Hannes Wellmann on 24/Mar/23 18:53 Exactly, please see also SLFJ4-579 for more background. Summed up, the intention is to allow libraries programmed against the slf4j-1 client api, which only import the package org.sfl4j with a version ranges like (1.x,2), to work with the slf4j-api in version 2 in OSGi runtimes as well. Therefore the slf4j.api bundle exports the package org.slf4j in version {{2.0.x}} and {{{}1.7.36{}}}. This is valid because the API in the org.slf4j package has not been broken from sfl4j-1 to 2 and slf4j is a drop-in replacement for slf4j-1 from the client perspective. Furthermore this allows much faster adoption of slf4j-2 in the OSGi world. Otherwise it would only be possible to update to slf4j-2 after all bundles of an application have been prepared for slf4j-2, which could take some time and could become complicated if libraries decide to require slf4j-2. Due to the nature of slf4j you don't want to slf4j.api bundles in your application. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af) _______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch https://mailman.qos.ch/cgi-bin/mailman/listinfo/slf4j-dev
