[jira] Closed: (SLING-1273) Launchpad Loader uses fragile file timestamp comparison to update launcher jar

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler closed SLING-1273.
-----------------------------------


> Launchpad Loader uses fragile file timestamp comparison to update launcher jar
> ------------------------------------------------------------------------------
>
>                 Key: SLING-1273
>                 URL: https://issues.apache.org/jira/browse/SLING-1273
>             Project: Sling
>          Issue Type: Bug
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.1.0
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>             Fix For:  Launchpad Base 2.2.0
>
>
> If the timestamp of the org.apache.sling.launchpad.base.jar file in the sling home folder is set in the future by mistake (like happens sometimes when copying/restoring the file), the Sling Loader will not upgrade it anymore, even if it has a more recent version.
> As that launcher jar is built as a bundle, we should use the bundle's Bnd-LastModified header (or even the full version number) to decide whether to update the launcher jar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.