[
https://issues.apache.org/jira/browse/SLING-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-6469.
-------------------------------------
Resolution: Fixed
If such a configuration entry is found it is not converted into the new "named
provider" property. Rev 1779044
> Resource Resolver Factory does not start if updating from an older version
> --------------------------------------------------------------------------
>
> Key: SLING-6469
> URL: https://issues.apache.org/jira/browse/SLING-6469
> Project: Sling
> Issue Type: Bug
> Affects Versions: Resource Resolver 1.5.10
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.5.12
>
>
> If the resource resolver bundle is updated and it exists a configuration for
> the "old" resource resolver factory, then this one contains usually a
> precondition on having the JCR resource provider. With the move to the new
> SPI this JCR resource provider does not use the PID anymore and therefore the
> precondition check fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
