I don't see how the issue you are encountering is related to DS. The issue is that you've declared that a subsystem has a content resource that cannot be found in one of the repositories. Be sure that a bundle with symbolic name co.diderot.staticresources and version in the range [0.0.3,0.0.4) is available. You can try packaging the bundle in the subsystem archive to see if that works.
On Mon, Oct 5, 2015 at 5:07 AM, Paul F Fraser <[email protected]> wrote: > All of my declarative services component bundles built using bndtools 3 in > eclipse Mars fail to install. > Bundles which do not use DS intall OK. > > I have tried adding the > Require-Capability: > osgi.extender;filter:="(&(osgi.extender=osgi.service.component)(version>=1.2.0)(!(version>=2.0.0)))" > to the bnd .bnd file but did not make any difference. > > The error, which has been discussed in earlier messages is as follows:- > > org.osgi.service.subsystem.SubsystemException: A required content resource > could not be found. This means the resource was either missing or not > recognized as a supported resource format due to, for example, an invalid > bundle manifest or blueprint XML file. Turn on debug logging for more > information. The resource was: > org.apache.aries.subsystem.core.archive.SubsystemContentRequirement: > namespace=osgi.identity, attributes={}, > directives={filter=(&(osgi.identity=co.diderot.staticresources)(type=osgi.bundle)(&(version>=0.0.3)(!(version>=0.0.4))))}, > resource=org.apache.aries.subsystem.core.internal.SubsystemResource@dd888a4e > > Is there anything about DS that could cause this to occur? There is some > mention a few years ago in bug reports about ds causing problems. > I am fairly confident that I am covering the dependencies in the subsystem > manifest. > > If there is not a known reason why this might be happening I will try to put > together a simple example. > > Regards > > Paul Fraser
