
Hello all, I pulled in changes made by Heiko http://github.com/ceki/slf4j/pull/2. Here is the version of the MANIFEST file from slf4j-api-1.6.1.jar. Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: ceki Build-Jdk: 1.6.0_16 Bundle-Description: The slf4j API Bundle-Version: 1.6.1 Implementation-Version: 1.6.1 Implementation-Title: slf4j-api Bundle-ManifestVersion: 2 Bundle-SymbolicName: slf4j.api Bundle-Name: slf4j-api Bundle-Vendor: SLF4J.ORG Bundle-RequiredExecutionEnvironment: J2SE-1.3 Export-Package: org.slf4j;version=1.6.1, org.slf4j.spi;version=1.6.1, org.slf4j.helpers;version=1.6.1 Import-Package: org.slf4j.impl;version=1.6.0 Here is the version generated after Heiko's changes have been applied: Manifest-Version: 1.0 Export-Package: org.slf4j.spi;uses:="org.slf4j";version="1.6.2.SNAPSHO T",org.slf4j.helpers;uses:="org.slf4j.spi,org.slf4j";version="1.6.2.S NAPSHOT",org.slf4j;uses:="org.slf4j.helpers,org.slf4j.spi";version="1 .6.2.SNAPSHOT" Ignore-Package: org.slf4j.impl Implementation-Title: slf4j-api Built-By: ceki Tool: Bnd-0.0.357 Bundle-Name: SLF4J API Module Created-By: Apache Maven Bundle Plugin Bundle-RequiredExecutionEnvironment: J2SE-1.4 Bundle-Vendor: QOS.ch Build-Jdk: 1.6.0_16 Bundle-Version: 1.6.2.SNAPSHOT Bnd-LastModified: 1288644768461 Bundle-ManifestVersion: 2 Bundle-License: http://www.opensource.org/licenses/mit-license.php Bundle-Description: The slf4j API Bundle-DocURL: http://www.qos.ch Bundle-SymbolicName: org.slf4j.api Import-Package: org.slf4j;version="[1.6.2.SNAPSHOT,1.7)",org.slf4j.hel pers;version="[1.6.2.SNAPSHOT,1.7)",org.slf4j.spi;version="[1.6.2.SNA PSHOT,1.7)" Admittedly, I am a little lost. The previous MANIFEST file imported org.slf4j.impl, whereas the latest MANIFEST does not. Strangely enough, org.slf4j.impl is not mentioned at all. In earlier message Heiko wrote:
As all the logging backends are fragments I excluded org.slf4j.impl package from imported packages. This means you can install the slf4j-api bundle in an OSGi container successfully without a backend. Not sure whether this is what we want.
I think it makes life easier if the slf4j-api bundle can be installed without a back-end. However, this is assuming that a desired back-end bundle can be installed and successfully bound with slf4j-api. (It is an obvious requirement but still may be useful to mention.) This version can be pulled in either from http://github.com/weiglewilczek/slf4j (master) or from http://github.com/ceki/slf4j (weiglewilczek-master). Your comments are most welcome, -- Ceki