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

Dominik Süß commented on SLING-5014:
------------------------------------

[~cziegeler] - patch has been refactored to be integrated in the installer core 
and  I created the corresponding PR.
https://github.com/apache/sling/pull/183

Note that the ITs  due to the nature of the OsgiInstaller currently take 2-3 
additional minutes due to necessary bundle restarts which are delayed by 
WABundleRefresher & PABundleRefresher (hardcoded 90second refresh timer).

> 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üß
>         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)

Reply via email to