[
https://issues.apache.org/jira/browse/SLING-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1995.
-------------------------------------
Resolution: Fixed
This seems to be fixed, therefore closing it
> Content Loader ignores bundles that were upgraded when the OSGi container was
> offline
> -------------------------------------------------------------------------------------
>
> Key: SLING-1995
> URL: https://issues.apache.org/jira/browse/SLING-1995
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR ContentLoader 2.1.2
> Reporter: Ian Boston
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
