That osgi.ee capability should be provided by the OSGi Framework itself. I don't quite see why Karaf needs to do this... I'm pretty sure that felix 4.4.0 provides this, but it may not be set on earlier versions...
See section 8.2 of the OSGi R5 Core spec. Cheers, David On 25 June 2014 14:12, Christian Schneider <ch...@die-schneider.net> wrote: > How is this done? Can it be done on an existing karaf version using just > configuration or do we need a new release? > > Christian > > > > On 25.06.2014 15:03, Achim Nierbeck wrote: >> >> We should add this requirement to the container as provided, since this >> will affect a lot of people using the maven-bundle-plugin 2.5 >> >> Regards, Achim >> >> sent from mobile device >> Am 25.06.2014 14:55 schrieb "Christian Schneider" >> <ch...@die-schneider.net>: >> >>> In our current build we seem to use the maven bundle plugin >>> 2.4.1-SNAPSHOT. >>> Since this version was changed I see a new Manifest header: >>> Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.6))" >>> >>> When I try to install such a bundle into karaf 2.3.5 (I tried with jpa >>> container 1.0.1-SNAPSHOT). I get the error that this requirement is not >>> met. >>> >>> So the question is should we avoid this header or should we add the >>> capability to the container in some way? >>> >>> Christian >>> >>> -- >>> Christian Schneider >>> http://www.liquid-reality.de >>> >>> Open Source Architect >>> http://www.talend.com >>> >>> > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com >
