You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/02/13 14:22:13 UTC

[jira] [Resolved] (SLING-2731) Bundle is sometimes not downgraded

     [ https://issues.apache.org/jira/browse/SLING-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2731.
-------------------------------------

    Resolution: Fixed

The attr is now cleared when a downgrade is detected. This should solve the problem
                
> Bundle is sometimes not downgraded
> ----------------------------------
>
>                 Key: SLING-2731
>                 URL: https://issues.apache.org/jira/browse/SLING-2731
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Core 3.4.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Installer Core 3.4.6
>
>
> If a bundle downgrade is detected, the bundle is sometimes not updated to the lower version, however the lower version is marked as installed.
> The installer uses an attr to mark a bundle resource to be started in the next phase (BundleUtil.ATTR_START). It seems that in previous versions of the installer, this attribute has not been cleared correctly. Therefore during a downgrade, the code first checks for this attr before it checks for the downgrade version. If the attribute is still present, the bundle is just started and marked as installed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira