[
https://issues.apache.org/jira/browse/SLING-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979626#comment-13979626
]
Carsten Ziegeler commented on SLING-3513:
-----------------------------------------
Actually my comment above is wrong and the problem is that the installer
expects an update of the full launchpad base jar (which totally makes sense in
a Sling world). However, this goes through Sling's version check mechanism and
in the end the version of the framework (e.g. 4.3.0) is compared with the
bundle version of the launchpad base jar (2.5.x) and therefore the update is
ignored as the new version (2.5.x) is lower.
I think the simplest way is to simply set the version of the launchpad base
bundle to the version of the framework
> Framework update not correctly detected
> ---------------------------------------
>
> Key: SLING-3513
> URL: https://issues.apache.org/jira/browse/SLING-3513
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Launchpad Base 2.5.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Launchpad Base 2.5.2
>
>
> When the framework is tried to be updated by the OSGi installer, it is
> sometimes not detected as a framework update. The code is checking the
> symbolic name to be system.bundle however, e.g. the Apache Felix framework
> uses org.apache.felix.framework as the symbolic name.
> It's better to check for the bundle id to be zero
--
This message was sent by Atlassian JIRA
(v6.2#6252)
