[
https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061659#comment-17061659
]
Konrad Windszus commented on SLING-9172:
----------------------------------------
It would be nice to mention explicity in the documentation what happens if the
property `sling.installer.multiversion=true` is toggled on an already existing
instance. What happens to the already installed artifacts? Are they gonna be
reinstalled, if yes, when exactly?
> Allow Sling Installer to install and handle multiple versions of bundles
> instead of updating
> --------------------------------------------------------------------------------------------
>
> Key: SLING-9172
> URL: https://issues.apache.org/jira/browse/SLING-9172
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Core 3.10.2
> Reporter: Dominik Süß
> Assignee: Carsten Ziegeler
> Priority: Major
> Labels: Sling-12-ReleaseNotes
> Fix For: Installer Core 3.11.0
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> Sling Installer currently always updates bundles when different versions of
> bundles get installed. Since Apache Felix does support multiple versions of
> bundles to exist in parallel it should be possible to change the behavior
> with via property to install and uninstall multiple versions in parallel
> instead of updating them.
> To achieve this two changes are required:
> a) DefaultTransformer should change the EntityID of bundles to include the
> version to make sure the state handling of Installer handles each version as
> own entity
> b) BundleTaskCreator must be adjusted to create install task over update task
> as the detection currently checks for the existence of BSN
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
