[
https://issues.apache.org/jira/browse/SLING-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-10815.
----------------------------------
Resolution: Won't Fix
Closing this issue - the number of generated capabilities increases
significantly without any real benefit. The servlets wrapping the scripts at
runtime will also be registered by path, so the resolution is not affected in
any way.
> Do not require the presence of a similarly named script as the resource type
> label to create a capability
> ---------------------------------------------------------------------------------------------------------
>
> Key: SLING-10815
> URL: https://issues.apache.org/jira/browse/SLING-10815
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Scripting Bundle Maven Plugin 0.5.0
>
>
> When analysing file-system projects the Scripting Bundle Maven Plugin should
> not require the presence of a similarly named script as the resource type
> label to create a resource type capability. The behaviour should be changed
> to generate the capability when:
> * an {{extends}} file is present OR
> * a {{.content.xml}} file that contains a {{sling:resourceSuperType}}
> property is present (SLING-10808) OR
> * a script that can be evaluated by a known Script Engine is present
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
