[
https://issues.apache.org/jira/browse/SLING-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635808#action_12635808
]
Felix Meschberger commented on SLING-683:
-----------------------------------------
> so we might also delegate the install/update decision to a service, to allow
> for customizable behavior.
I don't think, that this is required. Generally you need one single bundle
instance, so defaulting (and only supporting) the update of an existing bundle
by its symbolicname is IMHO appropriate.
There are some use cases, where you want multiple versions of the same bundle
installed at the same time. But this is tricky to do and we should not target
it in JCRInstall for the moment.
> jcrinstall cannot replace bundles installed by other means
> ----------------------------------------------------------
>
> Key: SLING-683
> URL: https://issues.apache.org/jira/browse/SLING-683
> Project: Sling
> Issue Type: Improvement
> Components: JCR Install
> Reporter: Bertrand Delacretaz
>
> Trying to update the webconsole via jcrinstall, for example, causes a second
> copy of the bundle to be installed, and that fails to register with the HTTP
> service, as the URL is already taken (which is fine).
> We could enable replacement of existing bundles by jcrinstall by having
> BundleResourceProcessor.installOrUpdate method check if a bundle exists in
> the OSGi framework, based on its Bundle-SymbolicName, compare versions with
> the incoming bundle, and update or install accordingly.
> That would prevent installing two different versions of the same bundle, so
> we might also delegate the install/update decision to a service, to allow for
> customizable behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
