You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/03/12 13:14:00 UTC
[jira] [Resolved] (SLING-9201) Files in nested resource tree
folders should only be analysed in the context of the closest resource type
[ https://issues.apache.org/jira/browse/SLING-9201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-9201.
---------------------------------
Resolution: Fixed
Fixed in [commit 29ad9df|https://github.com/apache/sling-scriptingbundle-maven-plugin/commit/29ad9df].
> Files in nested resource tree folders should only be analysed in the context of the closest resource type
> ---------------------------------------------------------------------------------------------------------
>
> Key: SLING-9201
> URL: https://issues.apache.org/jira/browse/SLING-9201
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Scripting Bundle Maven Plugin 0.2.0
>
>
> Files in nested resource tree folders should only be analysed in the context of the closest resource type, otherwise they might generate wrong capabilities.
> Example:
> {noformat}
> sling/
> components/
> a/
> a.html
> b/
> c/
> c.html
> d.html
> {noformat}
> In this setup the following resource types should be defined:
> # sling/components/a with selectors b.d
> # sling/components/a/b/c
--
This message was sent by Atlassian Jira
(v8.3.4#803005)