[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063137#comment-17063137 ] Carsten Ziegeler commented on SLING-9172: - After discussion on mailing list, renamed property to sling.installer.experimental.multiversion > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061816#comment-17061816 ] Bertrand Delacretaz commented on SLING-9172: Good point, I'll ask on our dev list what people think > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061811#comment-17061811 ] Carsten Ziegeler commented on SLING-9172: - [~bdelacretaz] If we think this is experimental we should probably rename the property to use "experimental" or something similar > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061792#comment-17061792 ] Bertrand Delacretaz commented on SLING-9172: For now I have marked this feature experimental at https://sling.apache.org/documentation/bundles/osgi-installer.html#multiversion-support and slightly reworded the docs > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061663#comment-17061663 ] Bertrand Delacretaz commented on SLING-9172: bq. 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. Good point! I think blocking this case, with the installer storing and refusing to change that setting, would be the safest option. > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061650#comment-17061650 ] Bertrand Delacretaz commented on SLING-9172: Thank you for the docs update. I'm tempted to label this feature as "experimental" in the docs, what do people think? It's very new, not tested extensively in the field and I'm a bit wary that it might expose weird issues. > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061630#comment-17061630 ] Carsten Ziegeler commented on SLING-9172: - Thanks [~dsuess] - lgtm > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061605#comment-17061605 ] Dominik Süß commented on SLING-9172: [~bdelacretaz], [~cziegeler], [~rombert] - created corresponding PR for docs linked to this: https://github.com/apache/sling-site/pull/44 > 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: 4h 20m > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[
https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17060961#comment-17060961
]
Bertrand Delacretaz commented on SLING-9172:
{quote}...I think it's also a big departure from how things worked so far, even
though opt-in, hence the suggestion for the version change..
{quote}
Big +1 to this, this might be a small change in terms of implementation but a
BIG thing in terms of changing existing assumptions.
As for the DynamicClassLoader I think we need at least a ticket for the changes
required there.
Regarding docs, please add at least a short note to
[https://sling.apache.org/documentation/bundles/osgi-installer.html] about this
feature, that shouldn't take more than a few minutes. The source of that page
is
https://github.com/apache/sling-site/blob/master/src/main/jbake/content/documentation/bundles/osgi-installer.md
> 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: 4h 10m
> 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17060939#comment-17060939 ] Robert Munteanu commented on SLING-9172: [~dsuess] - fully agree on not delaying the release with docs, but it should be there eventually. I think it's also a big departure from how things worked so far, even though opt-in, hence the suggestion for the version change. > 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: 4h 10m > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17060931#comment-17060931 ] Dominik Süß commented on SLING-9172: [~rombert] the change isn't as big as the default behavior doesn't change yet I can provide documentation on that - I yet don't see any need to delay a release of this as ootb nothing changes unless explicitly activating this feature. > 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: 4h 10m > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17060907#comment-17060907 ] Robert Munteanu commented on SLING-9172: [~dsuess] - would be great to see some documentation here, and I think we should reference this in the Sling 12 release notes as it's a big change. Next releases should probably be 3.11.0 to signal that. > 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.10.4 > > Time Spent: 4h 10m > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052006#comment-17052006 ] Konrad Windszus commented on SLING-9172: My concern is that this feature may break stuff once merged and activated. Therefore we should also fix the downstream consumers before merging this! > 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)
[jira] [Commented] (SLING-9172) Allow Sling Installer to install and handle multiple versions of bundles instead of updating
[ https://issues.apache.org/jira/browse/SLING-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051999#comment-17051999 ] Dominik Süß commented on SLING-9172: [~kwin] this is currently out of scope of this ticket - this is supposed to tackle certain scenarios like multiple version of libs. Yes in case of usage of those with dynamic classloader that might be not fully predictable - this ticket specifically just is about enabling controlling scenarios that can already be reflected with features and the corersponding launcher. Right now the installer can't be properly used for developing with such a setup due to the forced update behavior. Subsequent improvments to support this are more than welcome - specifically when we could establish some more strict binding between consumers of the dynamic classloader and the "providing" bundles. > 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: 20m > 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)
