[
https://issues.apache.org/jira/browse/ARIES-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477968#comment-13477968
]
John Ross commented on ARIES-870:
---------------------------------
First, I'm surprised the resolver thinks it needs to resolve the system bundle
as part of installing the subsystem. The subsystem's ResolveContext should be
returning the system bundle as part of the current wiring which means the
resolver should not attempt to resolve it. There might be a bug in the
ResolveContext.
Second, the workaround to any resolution failures due to a missing osgi.ee
capability is to have one of the subsystem's content bundles provide it. For
example, in this case, adding
Provide-Capability: osgi.ee;osgi.ee=JavaSE;version=1.5
to the manifest of one of the content bundles should get around this issue.
> How to handle osgi.ee requirements.
> -----------------------------------
>
> Key: ARIES-870
> URL: https://issues.apache.org/jira/browse/ARIES-870
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Reporter: John Ross
>
> When working with the Resolver in order to compute dependencies and resolve
> subsystems, the ResolveContext will need to handle requests for osgi.ee
> capabilities. Currently, these capabilities need to be provided by resources
> packaged with the subsystems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
