Hi, OSGi R8 (https://docs.osgi.org/javadoc/osgi.core/8.0.0/) defined org.osgi.service.log 1.5.0. However, for backward compatibility, pax-logging still uses org.osgi.service.log 1.4.0. So, either you extend the import version range to include 1.4.0 (it's what we did internally in Karaf), or we can add 1.5.0 export in pax-logging.
Regards JB On Tue, May 24, 2022 at 8:43 PM Steinar Bang <[email protected]> wrote: > > Current problem: I have problems satisfying the OSGi log service import > after moving to karaf 4.4.0 and OSGi 8. > > The integration test for a the bundle servlet.jersey fails with this > log trace: > https://gist.github.com/steinarb/2248cf2ebd8b72d6d2eec38891a7799c > > I have bumped the karaf BOM to 4.4.0, and split org.osgi/osgi.cmpn into > the needed invdivdual dependencies. The effective pom of the project > looks like this (dependency for the log service starting on line 2262): > https://gist.github.com/steinarb/73a913ae84124d152af4facacfba52db > > The resulting MANIFEST.MF of servlet.jersey, imports > org.osgi.service.log;version="[1.5,2)": > https://gist.github.com/steinarb/ca3a7e2aa4950e7d022e5c37a598d634 > > The karaf command package:list in the karaf 4.4.0 console, reports > org.osgi.service.log version 1.4.0 available: > org.osgi.service.log.admin │ 1.0.0 │ 6 │ > org.ops4j.pax.logging.pax-logging-api > org.osgi.service.log.stream │ 1.0.0 │ 6 │ > org.ops4j.pax.logging.pax-logging-api > org.osgi.service.log │ 1.4.0 │ 6 │ > org.ops4j.pax.logging.pax-logging-api > > So that explains why things won't load. > > But which one is right? The version in karaf 4.4.0 or the version in the > karaf BOM? >
