You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2019/11/15 06:24:00 UTC

[jira] [Created] (SLING-8848) Wrong calculation for copy/move whether single provider can be used

Carsten Ziegeler created SLING-8848:
---------------------------------------

             Summary: Wrong calculation for copy/move whether single provider can be used
                 Key: SLING-8848
                 URL: https://issues.apache.org/jira/browse/SLING-8848
             Project: Sling
          Issue Type: Bug
          Components: ResourceResolver
    Affects Versions: Resource Resolver 1.6.14
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Resource Resolver 1.6.16


When a copy/move is performed, the resource resolver checks whether a single provider can perform the copy/move or if sub providers exist (or source and dest have a different provider).
The checking for sub providers is currently wrong and leads to a copy/move being done "manually" (resource by resource)
Credits to Christian Keller for finding this and submitting a patch



--
This message was sent by Atlassian Jira
(v8.3.4#803005)