[jira] [Commented] (SLING-5014) Installer blacklist, to avoid reinstalling older bundles

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

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

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

Do we have any documentation on this?

I have a similar use case where I'd like to completely ignore some resources that are supplied to the installer, based on patterns in their URLs, when starting a fresh Sling instance.

Does this feature help for that?

> 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üß
>            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
(v6.3.4#6332)