[
https://issues.apache.org/jira/browse/SLING-10689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394023#comment-17394023
]
Konrad Windszus edited comment on SLING-10689 at 8/5/21, 1:53 PM:
------------------------------------------------------------------
In
https://github.com/apache/sling-scriptingbundle-maven-plugin/commit/76bf25f23fd3ce3d5381db7423a6c01909dcd075
this is resolved: The parser from Bnd is used to parse the {{extends}} file
which now supports an optional directive {{resolution:=optional}}. That
directive is emitted on the derived {{Require-Capabilities}} header as well.
was (Author: kwin):
In
https://github.com/apache/sling-scriptingbundle-maven-plugin/commit/76bf25f23fd3ce3d5381db7423a6c01909dcd075
the Parser from Bnd was used to parse the extends file which now supports an
optional directive "resolution:=optional". That directive is emitted on the
derived "Require-Capabilities" header as well.
> Extends file must not always generate a mandatory 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)
