Hi John, Thanks for the response. I've created the issue: https://issues.apache.org/jira/browse/ARIES-1368
Best regards, Wouter Bancken 2015-08-06 19:54 GMT+02:00 John W Ross <[email protected]>: > I've been away for awhile and have forgotten much of the unofficial history, > but this does seem like a bug to me. The BundleResource is hardcoded to > always assume a type of osgi.bundle without inspecting the manifest. I can't > think of a reason offhand why we shouldn't expect folks to package bundle > fragments into an ESA as part of the content. Would you mind opening a JIRA > [1] for further discussion, please? > > The only work-around I can think of would be to list the bundle fragments as > part of the Subsystem-Content header but make them available from a > repository rather than including the JARs in the ESA itself. You could also > install them programmatically using your subsystem's bundle context. > > [1] https://issues.apache.org/jira/browse/ARIES/ > > Wouter Bancken <[email protected]> wrote on 08/06/2015 02:11:41 AM: > >> From: Wouter Bancken <[email protected]> >> To: [email protected] >> Date: 08/06/2015 02:12 AM >> Subject: BundleResource not able to compute capabilities for fragments > > >> >> Dear, >> >> I'm trying to deploy a subsystem but I'm experiencing some issues due >> to the computeOsgiIdentityCapability method of the BundleResource not >> being able to compute capabilities for fragments (only for bundles). >> Was there a motivation behind this behavior or is this a bug in the >> Aries implementation? >> >> Best regards, >> Wouter Bancken >>
