Hello There's (still) unresolved https://github.com/ops4j/org.ops4j.pax.logging/issues/410 issue. And yes - Pax Logging exports at most version 1.4 because there were no big reasons to bump this version... However I agree that users with org.osgi.service.log 1.5 on the classpath will have "[1.5,2)" generated by maven-bundle-plugin...
regards Grzegorz Grzybek pt., 15 lip 2022 o 13:04 Steinar Bang <[email protected]> napisał(a): > >>>>> Jean-Baptiste Onofré <[email protected]>: > > > On Wed, May 25, 2022 at 5:02 PM Steinar Bang <[email protected]> wrote: > > >> >>>>> Jean-Baptiste Onofré <[email protected]>: > > >>> 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. > > >> I'd say add 1.5.0 export in pax-logging. > > >> My assumption is that the versions picked by the karaf BOM should work > >> out of the box. > > >> But for now I'll extend the range to include 1.4.0. > > > Fair enough, I will create a Jira/issue about that. > > Karaf 4.4.1 still seems to be only exporting logging service 1.4.0. > > I bumped the karaf BOM to 4.4.1 and rebuilt and everything went fine. > > I then removed the explicit logging service 1.4.0 imports from the > maven-bundle-plugin configs and rebuilt with "mvn clean install", and > then my app failed in the pax exam test: > https://gist.github.com/steinarb/4ac22fb118e6bca3170971c6d1443b1a > >
