[
https://issues.apache.org/jira/browse/SLING-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974845#comment-16974845
]
Carsten Ziegeler edited comment on SLING-8848 at 11/15/19 6:27 AM:
-------------------------------------------------------------------
Fixed in
https://github.com/apache/sling-org-apache-sling-resourceresolver/commit/c571ac6a9feea403e65d1bb5f68ab6638d20009b
And added more tests that verify the behaviour - the previous tests for
copy/move did not detect the wrong calculation
was (Author: cziegeler):
Fixed in
https://github.com/apache/sling-org-apache-sling-resourceresolver/commit/c571ac6a9feea403e65d1bb5f68ab6638d20009b
> 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
> Priority: Major
> 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)
