[ https://issues.apache.org/jira/browse/SLING-10706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394848#comment-17394848 ]
Radu Cotescu commented on SLING-10706: -------------------------------------- In the classical setup (scripts in the repository) how would you define a script mapped to a list of identical selectors without doing weird things? To my knowledge, as soon as you have more than one selector to which you want to map a script you will end up with folder structures, e.g.: {noformat} /apps/scripts/myscript myscript.html sel1/sel2.html {noformat} If you had something like: {noformat} /apps/scripts/myscript myscript.html sel1/sel1.html {noformat} then I think that we'd talk about two resource types: {{scripts/myscript}} and {{scripts/myscript/sel1}}. > 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)