[
https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052027#comment-17052027
]
Dominik Süß commented on SLING-9172:
------------------------------------
I don't agree - this is the reason why the default behavior is the same.
Pushing back adaption will lead to development scenarios composed of dozens of
snapshots and complicates synchronization. This is following the practice of
short iterations and tackling one issue at a time instead of overloading an
upstream change with all the downstream dependencies - toggling off the new
behavior by default and only activating by default soon as everything works is
a common pattern far better documenting the remaining work.
> 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üß
> Priority: Major
> Time Spent: 0.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)
