[
https://issues.apache.org/jira/browse/FELIX-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113390#comment-13113390
]
Neil Bartlett commented on FELIX-2465:
--------------------------------------
I think this does need to be fixed, but it's quite simple to do.
When running on Equinox, the resolver creates a capability for the system
bundle with "symbolicname=org.eclipse.osgi". If a bundle or fragment does the
*right* thing, e.g. "Require-Bundle: system.bundle" or "Fragment-Host:
system.bundle" then the requirement does not resolve. However, bundles that do
the *wrong* thing and specify their dependency on "org.eclipse.osgi" do resolve.
The fix should be to always create a capability of type "bundle" with
"symbolicname=system.bundle", in addition to the existing capability that
provides the framework-specific name.
> system.bundle should be automatically wired to the relevant bundle
> ------------------------------------------------------------------
>
> Key: FELIX-2465
> URL: https://issues.apache.org/jira/browse/FELIX-2465
> Project: Felix
> Issue Type: Bug
> Components: Bundle Repository (OBR)
> Affects Versions: bundlerepository-1.4.2
> Environment: n/a
> Reporter: Emily Jiang
>
> When provisioning, it would be nice to automatically treat system.bundle as
> the system bundle symbolic name, so that users don't need to rely on the
> particular system bundle. For an example, in equinox, the system.bundle
> should be treated the same as the org.eclipse.osgi.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
