[
https://issues.apache.org/jira/browse/SLING-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738989#comment-14738989
]
Dominik Süß commented on SLING-5014:
------------------------------------
[~cziegeler] - ok so we just detect that the installable is gone right? Could
you please point me to the code that processes the uninstall directive in the
launchpad so I can check if my conclusion based on the observed behavior was
really correct. Anyways I think I got your point that we need something
additional to "persist" this uninstall information as all the metainformation
stored in the model is lost in the process of the subsequent events that
finally lead to the persisted osgi installer state.
> 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)
