[jira] [Commented] (SLING-10689) Extends file must not always generate a Requires-Capability header

["Radu Cotescu (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-10689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392170#comment-17392170 ] 

Radu Cotescu commented on SLING-10689:
--------------------------------------

bq. to support more parameters than just version ... without relying on the order.

Sure, but my question was more about why should the parser be stricter? Anyways, I need a bit more time to manage to review your changes - I have some other pressing things to take care of right now. Are you in a hurry to get this merged?

> Extends file must not always generate a Requires-Capability header
> ------------------------------------------------------------------
>
>                 Key: SLING-10689
>                 URL: https://issues.apache.org/jira/browse/SLING-10689
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>    Affects Versions: Scripting Bundle Maven Plugin 0.3.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Scripting Bundle Maven Plugin 0.4.0
>
>
> The  {{extends}} file is necessary for bundled scripts as this generates the {{extends}} attribute of the {{sling.servlet}} capability (which is the only way to express inheritance). Currently the scriptingbundle-maven-plugin always also generates an according {{Require-Capability}} header (https://sling.apache.org/components/scriptingbundle-maven-plugin/). The latter can only be resolved in case the script it extends from is provided as bundled script as well, but not if it is a regular resource script. Therefore there must be an option in the extends file to not generate the Require-Capability header.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)