You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Artyom Stetsenko (JIRA)" <ji...@apache.org> on 2014/06/05 15:01:03 UTC

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

Artyom Stetsenko created SLING-3648:
---------------------------------------

             Summary: 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: Improvement
          Components: JCR
    Affects Versions: JCR ContentLoader 2.1.2
            Reporter: Artyom Stetsenko
             Fix For: JCR ContentLoader 2.1.4


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)