[
https://issues.apache.org/jira/browse/SLING-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738901#comment-14738901
]
Dominik Süß commented on SLING-5014:
------------------------------------
[~cziegeler] ok - to rephrase. The uninstall directive leads to a corresponding
uninstall task which afaiu only uninstalls the currently installed version of
the bundle leading to a downgrade. I yet haven`t found the mechanism that
generates the uninstall task for this directive - probably this uninstall task
would need to be able to provide further metadata to define if only the
currently installed needs to be removed (leading to a downgrade) or if a whole
range is about to be removed, making the osgi installer aware which versions
would be valid for installation and which ones need to be "blacklisted".
> 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
> Reporter: Dominik Süß
>
> 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)
