[
https://issues.apache.org/jira/browse/SLING-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588191#comment-15588191
]
Dominik Süß commented on SLING-5014:
------------------------------------
Pullrequest has been updated based on feedback by [~cziegeler] - as invocation
chain leads to the case that the implementation will always be
EntityResourceList casting is an appropriate way to prevent API changes but
rely on the internal implementation details and just introduce the new method
in there.
> 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üß
> Fix For: Installer Core 3.6.10
>
> 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)
