[SLING-3648] CLONE - Content Loader ignores bundles that were upgraded when the OSGi container was offline

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR ContentLoader 2.1.8
• Component/s: JCR
• Assignee: Bertrand Delacretaz
• Reporter: Artyom Stetsenko
• Created: 05/Jun/14 12:59
• Updated: 03/Jul/14 14:22
• Resolved: 03/Jul/14 14:22

Description

If a bundle is updated when the OSGi container is offline or as a result of an update during startup, the content loader does not consider the bundle to have been updated and consequently does not inspect the new content to see if it should be loaded.

I have a patch, that uses the bundle last modified date (bound to when it was installed) and the content loaded at timestamp on the bundle registration node to determine if the bundle should be reloaded. It appears to work for me, waiting for on list review before committing.

Issue Links

• is a clone of: SLING-1995 Content Loader ignores bundles that were upgraded when the OSGi container was offline