[SLING-1273] Launchpad Loader uses fragile file timestamp comparison to update launcher jar

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Launchpad Base 2.1.0
• Fix Version/s: Launchpad Base 2.2.0
• Component/s: Launchpad
• Assignee: Bertrand Delacretaz
• Reporter: Bertrand Delacretaz
• Created: 06/Jan/10 15:19
• Updated: 10/Dec/10 15:37
• Resolved: 20/Apr/10 12:15

Description

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.

Issue Links

• is blocked by: SLING-1278 Utilities for bundle version comparison, handling both jar files and Bundle objects