[
https://issues.apache.org/jira/browse/SLING-10706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17395198#comment-17395198
]
Radu Cotescu commented on SLING-10706:
--------------------------------------
bq. Does that mean, that this plugin will never register more than 1 selector
for a single script? That would be an even bigger flaw then...
I didn't say that. I said that nested identical selectors via folder + script
file with the same name won't generate the capability you expect. In addition
to that, the scripts of a nested resource type won't generate selectors for a
resource type folder containing it. For this second observation see [0].
[0] -
https://github.com/apache/sling-scriptingbundle-maven-plugin/blob/76bf25f23fd3ce3d5381db7423a6c01909dcd075/src/main/java/org/apache/sling/scriptingbundle/plugin/processor/ResourceTypeFolderAnalyser.java#L72
> Order of selectors not kept
> ---------------------------
>
> Key: SLING-10706
> URL: https://issues.apache.org/jira/browse/SLING-10706
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
> Affects Versions: Scripting Bundle Maven Plugin 0.3.0
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: Scripting Bundle Maven Plugin 0.4.0
>
>
> The selectors used for registration of script/servlets have an order: Only if
> they appear in the given order the script/servlet matches
> (https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-registration).
> The order is potentially lost, though during the generation of the
> capabilities headers as the code is using Sets internally.
> Also it is totally valid to register a script to "myselector.myselector"
> which cannot be expressed with Sets either.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
