[
https://issues.apache.org/jira/browse/SLING-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artyom Stetsenko updated SLING-3648:
------------------------------------
Attachment: SLING-3648.patch
Attached patch.
The fix from the original issue enabled the call to
{{Loader#installContent(...)}} but seems to have missed that there is another
check there.
> CLONE - Content Loader ignores bundles that were upgraded when the OSGi
> container was offline
> ---------------------------------------------------------------------------------------------
>
> Key: SLING-3648
> URL: https://issues.apache.org/jira/browse/SLING-3648
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR ContentLoader 2.1.8
> Reporter: Artyom Stetsenko
> Attachments: SLING-3648.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
