>>>>> Jean-Baptiste Onofré <[email protected]>: > Fair enough, I will create a Jira/issue about that.
Another thing that maybe should be added to that issue is the capability osgi.extender. I've never understood what a capability is, and how it's related to features and bundles, but for some reason one of my bundles, when ported to karaf 4.4.0 and OSGi 8 fails because it can't find the capability osgi.extender in the range >=1.5.0 and <2.0.0: https://gist.github.com/steinarb/de15776fb4abf2b5d11c56c04bb176c1 And since the capabilities command in the karaf console contains: osgi.extender; osgi.metatype 1.4.0 [UNUSED] I guess this is something similar to what happened to the log service? I tried fixing this by adding <Require-Capability>osgi.service;filter:="(objectClass=javax.sql.DataSource)";effective:=active,osgi.service;filter:="(objectClass=org.osgi.service.log.LogService)";effective:=active,osgi.extender;filter:="(&(osgi.extender=osgi.component)(version>=1.4.0)(!(version>=2.0.0)))",osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=11))"</Require-Capability> to the maven-bundle-plugin config. But that just added the stuff in <Require-Capability> to the existing stuff in the Require-Capability header in the MANIFEST.MF, so the load issue persisted with the same cause given: Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=11))",os gi.extender;filter:="(&(osgi.extender=osgi.component)(version>=1.4.0)(! (version>=2.0.0)))",osgi.service;filter:="(objectClass=javax.sql.DataSo urce)";effective:=active,osgi.service;filter:="(objectClass=org.osgi.se rvice.log.LogService)";effective:=active,osgi.service;filter:="(objectC lass=org.osgi.service.log.LogService)";effective:=active,osgi.extender; filter:="(&(osgi.extender=osgi.component)(version>=1.5.0)(!(version>=2. 0.0)))"
