[
https://issues.apache.org/jira/browse/SLING-12813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955228#comment-17955228
]
Julian Reschke commented on SLING-12813:
----------------------------------------
The problem is caused by the change to walk up the tree using Resources, not
paths.
This fails once a parent is null due to access control.
> Regression in resource resolver
> -------------------------------
>
> Key: SLING-12813
> URL: https://issues.apache.org/jira/browse/SLING-12813
> Project: Sling
> Issue Type: New Feature
> Reporter: Carsten Ziegeler
> Assignee: Julian Reschke
> Priority: Major
> Fix For: Resource Resolver 2.0.0, Resource Resolver 1.12.10
>
>
> Using the latest resource resolver (2.0.0-SNAPSHOT as well as
> 1.12.9-SNAPSHOT) fails one of the Sling Starter test cases. This one passes
> with 1.12.8 - looks like a regression
> {code:java}
> [ERROR] Failures:
> [ERROR]
> ResourceResolverGeneralTest.test_resolve_with_sling_alias_limited_access:2593
> expected:</[child/]enkel> but was:</[]enkel>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
