sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Kuijpers (JIRA)" <>
Subject [jira] [Commented] (SLING-5014) Installer blacklist, to avoid reinstalling older bundles
Date Thu, 30 Mar 2017 15:17:41 GMT


Henry Kuijpers commented on SLING-5014:

Is it also possible to make exceptions to this installer blacklist? I.e. the sling_bootstrap.txt
says that certain bundles must be uninstalled (upgraded AEM), but we are still installing
these bundles and requiring them (feature not yet upgraded after upgrade).

> Installer blacklist, to avoid reinstalling older bundles
> --------------------------------------------------------
>                 Key: SLING-5014
>                 URL:
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Core 3.6.6
>            Reporter: Dominik Süß
>            Assignee: Carsten Ziegeler
>             Fix For: Installer Core 3.7.0
>         Attachments: SLING-5014-1.diff
> In case a bundle has mutliple install candiates only the highest version (with the highest
priorty for the same versions) wins. An uninstall directive in the Sling bootstrap.txt file
or provisioning model uninstalls this version. The way the OSGi install behavior is defined
this lets the next artifact in the priority queue to get active and consequently only leads
to downgrade to the next in the queue.
> As the uninstall directive declares a range that should be uninstalled the expectation
is that after a startup with such an uninstall directive none of the declared versions are
in an installed state. In consequence the OSGi installer must save this metainformation in
the state that prevents a downgrade to a version that is part of an active uninstall directive.

This message was sent by Atlassian JIRA

View raw message