[SLING-1663] OSGi Install should recognize system bundle updates

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Installer Core 3.0.0
• Component/s: Installer
• Assignee: Carsten Ziegeler
• Reporter: Felix Meschberger
• Created: 17/Aug/10 14:36
• Updated: 20/Sep/17 12:13
• Resolved: 10/Sep/10 09:20

Description

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