[
https://issues.apache.org/jira/browse/SLING-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988385#comment-14988385
]
Dominik Süß commented on SLING-5014:
------------------------------------
[~cziegeler] - this patch is more about granting that the uninstall directives
really are taken into account. Although the OSGi config allows to override the
uninstall directives as blacklist definitions the current implementation does
not prevent uninstallation by the bootstrap installer on next startup.
We could think about an alternative way of defining the "amendment"/override of
sling_bootstrap.txt in an install location that would need to be looked up
before the bootstrap installer kicks in. This definition then should be
respected by the blacklist service as well (just like utilizing
sling_bootstrap.txt right now)
It would anyways be great if you could have a quick look at my implementation
as I want to make sure I haven't missed scenarios.
Note: this is more of a safety net for scenarios where installables are present
that shouldn't be installed. The various different ways we have to provide
installables lead to a state where it is not unlikely (and multiple time
observed) that this safety net needs to kick in.
> 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)
