[ 
https://issues.apache.org/jira/browse/SLING-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000306#comment-15000306
 ] 

Bertrand Delacretaz commented on SLING-5014:
--------------------------------------------

bq. this is more of a safety net for scenarios where installables are present 
that shouldn't be installed.

It looks like this is the root cause: unwanted installable bundles being 
present in the content repository and (correctly) picked up by the installer.

Shouldn't we rather provide a way to cleanly remove those unwanted installables 
from the repository? I've seen several upgrade-related cases where a 
"repository cleanup" phase would be useful to get rid of leftovers from 
previous versions before making the repository service available. We might 
implement such a cleanup phase (with extension points) as a generally useful 
upgrade-related feature, and avoid complicating the installer even more with a 
blacklist than in the end is just a workaround for this "stale installables" 
issue.

> Installer blacklist, to avoid reinstalling older bundles
> --------------------------------------------------------
>
>                 Key: SLING-5014
>                 URL: https://issues.apache.org/jira/browse/SLING-5014
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Core 3.6.6
>            Reporter: Dominik Süß
>         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
(v6.3.4#6332)

Reply via email to