Remove unneded OSGi compendium API exports from Sling Launcher (system bundle)
------------------------------------------------------------------------------
Key: SLING-1094
URL: https://issues.apache.org/jira/browse/SLING-1094
Project: Sling
Issue Type: Improvement
Components: Launchpad Launcher
Affects Versions: Launchpad Base 2.0.4
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Launchpad Base 2.0.6
Currently the Sling launcher includes all OSGi core and compendium packages and
exports them through the system bundle. On the other hand the OSGi service
implementations by Apache Felix (Configuration Admin, Declarative Services,
etc.) and oursevles (LogService) all include the actual API package version the
implement as an export.
Now, that Apache Felix Configuration Admin is implementing the next verison of
the configuration admin specification (1.3) and Apache Felix Declarative
Services trunk the next version of the declarative services specification (1.1)
this creates issues when upgrading the respective bundles in existing
installations:
* The new bundles wire themselves to their own exports (because the version
is higher than the system bundle export)
* Running bundles are *not* rewired to the new exports
Only when explicitily asking the respective client bundles to rewire or when
restarting the framework will wiring to the new versions be fixed.
This presents a real problem to running installations and is kind of unbearable
in the spirit of OSGi.
For this reason, the OSGi compendium export from the system bundle (by way of
the Sling launcher) must be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
