[
https://issues.apache.org/jira/browse/SLING-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-3307:
---------------------------------------
Assignee: Carsten Ziegeler
> Updated launchpad bundle list is not reflected after upgrade
> ------------------------------------------------------------
>
> Key: SLING-3307
> URL: https://issues.apache.org/jira/browse/SLING-3307
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Affects Versions: Launchpad Installer 1.2.2
> Reporter: Robert Munteanu
> Assignee: Carsten Ziegeler
> Attachments: SLING-3307-repro.zip
>
>
> This is a follow-up bug report for
> http://markmail.org/thread/6us2jyrkcz6wjwxr .
> I've run into a bug when trying to update an existing Sling launchad to add a
> new bundle. The steps I've taken were:
> * Create a launchpad ( using the maven-launchpad-plugin ) and executed the
> jar file
> * Updated the bundle list to include a new bundle and executed the jar file
> on top of the existing launchpad directory
> The end result was that the new bundle was not deployed.
> Digging in the code a bit, I've noticed that the upgrade goes well if I force
> the startup mode to update.
> The sling/conf/launchpad_timestamp.txt exists and is valid. It seems that the
> StartupManager.getSelfTimeStamp() method does not get the correct timestamp:
> * looks for the last-modified date of the jar loading StartupManager.class -
> org.apache.sling.launchpad.base.jar
> * looks for the last-modified date of the jar loading
> LaunchpadContentProvider.class - still org.apache.sling.launchpad.base.jar
> * looks for the last-modified date of all the bundles from sling/startup
> folder
> The problem is that at this point, the new/modified bundles are not present
> in the sling/startup folder, so they are not taken into account.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
