[
https://issues.apache.org/jira/browse/FELIX-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404716#comment-13404716
]
Dan Gravell commented on FELIX-2465:
------------------------------------
Coming from a hybrid Equinox development, Felix runtime environment this is
really useful. Right now, when I update a bundle depending on a system bundle
fragment, I *have* to update the fragment with a spurious version update,
otherwise the LocalResourceImpl is used, which requires system.bundle (because
system.bundle is the requirement in the Manifest) and OBR promptly fails to
resolve the requirements.
I realise there are very few changes from 1.6.6 so far, but if this could be
rolled into a 1.6.8 release it would be great. There's no nightly build that
I've found.
> 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
> Assignee: Richard S. Hall
> Fix For: bundlerepository-1.6.8
>
> Attachments: patch.FELIX-2465.txt
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
