[
https://issues.apache.org/jira/browse/SLING-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901854#action_12901854
]
Carsten Ziegeler commented on SLING-1663:
-----------------------------------------
Added a first implementation in revision 988515 - not tested yet
> OSGi Install should recognize system bundle updates
> ---------------------------------------------------
>
> Key: SLING-1663
> URL: https://issues.apache.org/jira/browse/SLING-1663
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Reporter: Felix Meschberger
> Assignee: Carsten Ziegeler
> Fix For: OSGi Installer 3.0.0
>
>
> The Launchpad Base module generates a bundle with the symbolic name
> "system.bundle" which is an official alias for the symbolic name of the
> system bundle whose real symbolic name is framework specific. The Web Console
> supports updates with the "system.bundle" symbolic name and updates the
> system bundle accordingly.
> The OSGi Installer should also recognize this situation and act accordingly:
> * The system bundle does not need to be stopped/started for the update, a
> framework restart is done automatically
> * A package refresh is not required
> * System bundle update acts immediately preventing OSGi Install from
> properly cleaning up after the install
> Thus updating the system bundle should probably be done in a special way:
> * at the of a processing cycle of OSGi Install
> * preventing any more processing before calling bundle update
> * probably updating the system bundle in a separate thread to not prevent
> proper shutdown of OSGi Install
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
