[
https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696246#comment-15696246
]
Konrad Windszus commented on SLING-6327:
----------------------------------------
The reason is that resource resolver in version 1.5.5-SNAPSHOT is used
(https://github.com/apache/sling/blob/trunk/launchpad/builder/src/main/provisioning/sling.txt#L60)
but still API in 2.15.0
(https://github.com/apache/sling/blob/trunk/launchpad/builder/src/main/provisioning/sling.txt#L36).
The RR now has a dependency to 2.15.1-SNAPSHOT!
What is the reason why launchpad relies on the latest SNAPSHOT of the resource
resolver?
> ResourceResolverImpl.isResourceType() should compare relative resource types
> (and ignore any search path prefixes)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-6327
> URL: https://issues.apache.org/jira/browse/SLING-6327
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Affects Versions: API 2.15.0, Resource Resolver 1.5.2
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: API 2.15.2, Resource Resolver 1.5.6
>
> Attachments: SLING-6327-v01.patch
>
>
> Currently the following two expressions return false
> {{ResourceResolverImpl.isResourceType(<Resource with
> resourceType="sling/some/type">, "/libs/sling/some/type"}}
> {{ResourceResolverImpl.isResourceType(<Resource with
> resourceType="/libs/sling/some/type">, "sling/some/type"}}
> Since it cannot always be influenced whether the given resource is absolute
> or relative (because both usually works from a rendering perspective when you
> talk about the current request's resource), both cases should actually return
> {{true}}.
> See also the related discussion at
> http://www.mail-archive.com/[email protected]/msg62351.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
