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 (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/22 15:30:40 UTC

[jira] [Resolved] (SLING-2290) Updating a fragment with a different version but the same content does not work

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

Carsten Ziegeler resolved SLING-2290.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: Installer Core 3.2.4

Fixed in revision 1205016 - the problem was due to the attempt of stopping a fragment before the actual update.
I've also refactored the code a little bit to make it cleaner and change the package refresh handling to a minimum.
                
> Updating a fragment with a different version but the same content does not work
> -------------------------------------------------------------------------------
>
>                 Key: SLING-2290
>                 URL: https://issues.apache.org/jira/browse/SLING-2290
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>    Affects Versions: Installer Core 3.2.4, JCR Installer 3.1.2
>            Reporter: Konrad Windszus
>            Assignee: Carsten Ziegeler
>             Fix For: Installer Core 3.2.4
>
>         Attachments: simplebundle-0.0.1-SNAPSHOT.jar, simplebundle-0.0.2-SNAPSHOT.jar, simplebundle-0.0.2-SNAPSHOT.jar
>
>
> If you update a bundle through a JCR package, it is only updated in Apache Felix if the actual content has changed. It is not enough to have the version number changed. This is a problem, because usually in multimodule maven builds I increase the version for all contained bundles although they might not have changed in that release. Unfortunately the new version is not deployed, therefore the Webconsole still shows the old version.
> The same problem applies to Bundle Fragments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira