You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Created) (JIRA)" <ji...@apache.org> on 2011/11/17 15:26:52 UTC
[jira] [Created] (SLING-2290) Updating a bundle with a different
version but the same content does not work
Updating a bundle 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
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
[jira] [Closed] (SLING-2290) Updating a fragment with a different
version but the same content does not work
Posted by "Carsten Ziegeler (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-2290.
-----------------------------------
> 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.3.0, JCR Installer 3.1.2
> Reporter: Konrad Windszus
> Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.3.0
>
> 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
[jira] [Commented] (SLING-2290) Updating a bundle with a different
version but the same content does not work
Posted by "Konrad Windszus (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152103#comment-13152103 ]
Konrad Windszus commented on SLING-2290:
----------------------------------------
It has a different filename (containing the version). I use the following versions
- org.apache.sling.installer.core in version 3.2.3.R1161029
- org.apache.sling.installer.provider in version 3.1.1.R1159543
> Updating a bundle 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
>
> 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
[jira] [Updated] (SLING-2290) Updating a fragment with a different
version but the same content does not work
Posted by "Carsten Ziegeler (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-2290:
------------------------------------
Summary: Updating a fragment with a different version but the same content does not work (was: Updating a bundle with a different version but the same content does not work)
Changing title
> 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
> 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
[jira] [Updated] (SLING-2290) Updating a bundle with a different
version but the same content does not work
Posted by "Konrad Windszus (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-2290:
-----------------------------------
Attachment: simplebundle-0.0.2-SNAPSHOT.jar
simplebundle-0.0.1-SNAPSHOT.jar
Found out that this wrong behaviour can only be reproduced with bundle-fragments. I attached both versions. Just upload version 0.0.1-SNAPSHOT first. After that upload version 0.0.2-SNAPSHOT. You can see that still the old version is deployed inside Apache Felixe
> Updating a bundle 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
> Attachments: simplebundle-0.0.1-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
[jira] [Commented] (SLING-2290) Updating a bundle with a different
version but the same content does not work
Posted by "Felix Meschberger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152109#comment-13152109 ]
Felix Meschberger commented on SLING-2290:
------------------------------------------
> It has a different filename (containing the version).
The filename is irrelevant. Important is, what is declared in the manifest inside the file. If that version is not modified, the bundle is considered not modified and thus not updated.
> Updating a bundle 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
>
> 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
[jira] [Commented] (SLING-2290) Updating a fragment with a
different version but the same content does not work
Posted by "Carsten Ziegeler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155279#comment-13155279 ]
Carsten Ziegeler commented on SLING-2290:
-----------------------------------------
Thanks Konrad for your test case!
> 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
[jira] [Resolved] (SLING-2290) Updating a fragment with a different
version but the same content does not work
Posted by "Carsten Ziegeler (Resolved) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (SLING-2290) Updating a bundle with a different
version but the same content does not work
Posted by "Carsten Ziegeler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152108#comment-13152108 ]
Carsten Ziegeler commented on SLING-2290:
-----------------------------------------
Ok, thanks - would it be possible to attach two versions of a sample bundle - you can also send them directly to me if you prefer.
In addition you could try latest from trunk as I improved some parts
> Updating a bundle 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
>
> 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
[jira] [Updated] (SLING-2290) Updating a bundle with a different
version but the same content does not work
Posted by "Konrad Windszus (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-2290:
-----------------------------------
Attachment: simplebundle-0.0.2-SNAPSHOT.jar
This JAR really has the correct Metadata but still the problem persists.
> Updating a bundle 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
> 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
[jira] [Commented] (SLING-2290) Updating a bundle with a different
version but the same content does not work
Posted by "Carsten Ziegeler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152090#comment-13152090 ]
Carsten Ziegeler commented on SLING-2290:
-----------------------------------------
If you change the bundle version, than the contents of the bundle changes as the version is included in the jar.
> Updating a bundle 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
>
> 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
[jira] [Assigned] (SLING-2290) Updating a fragment with a different
version but the same content does not work
Posted by "Carsten Ziegeler (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reassigned SLING-2290:
---------------------------------------
Assignee: Carsten Ziegeler
> 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
> 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
[jira] [Commented] (SLING-2290) Updating a bundle with a different
version but the same content does not work
Posted by "Konrad Windszus (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152093#comment-13152093 ]
Konrad Windszus commented on SLING-2290:
----------------------------------------
Yes that is right, but still the bundle is not updated! I don't know whether this is related to the Sling Installer or Apache Felix itself, but you can easily reproduce by just increasing the version of a bundle and change nothing else and deploy that to a JCR. You can see that the bundle is not updated within Apache Felix, although it should be.
> Updating a bundle 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
>
> 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
[jira] [Commented] (SLING-2290) Updating a bundle with a different
version but the same content does not work
Posted by "Carsten Ziegeler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152098#comment-13152098 ]
Carsten Ziegeler commented on SLING-2290:
-----------------------------------------
So, you put a changed bundle with a new version number into the repository and it doesn't get updated, right?
Do you use the same filename or is something like the version included in the filename?
Are you using the latest release or latest from trunk?
> Updating a bundle 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
>
> 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