[jira] [Commented] (SLING-5014) Uninstall directive in provisioning model might just lead to downgrade of bundle

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler commented on SLING-5014:
-----------------------------------------

We definitely need a way where you can override the info from the uninstall section. We already had the use case where someone wanted to reinstall a bundle which was removed by the uninstall section on startup

> Uninstall directive in provisioning model might just lead to downgrade of bundle
> --------------------------------------------------------------------------------
>
>                 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 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 delcared 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)