[
https://issues.apache.org/jira/browse/SLING-10129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283692#comment-17283692
]
Bertrand Delacretaz commented on SLING-10129:
---------------------------------------------
I'm not too keen on skipping statements if an older version of the parser
executes newer code, because:
0) repoinit statements are often related to security, I think introducing
conditionals can lead to overlooking important things
1) if we introduce a new {{REQUIRE language.version N.NN}} statement, parsing
will fail with older versions anyway
I would much prefer loudly failing if statements are not supported by the
current parser - you can then either remove the corresponding repoinit fragment
from your configuration or update the parser.
> Introduce version statement
> ---------------------------
>
> Key: SLING-10129
> URL: https://issues.apache.org/jira/browse/SLING-10129
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Reporter: Konrad Windszus
> Priority: Major
>
> Although with SLING-9186 it is now easy to enforce that repoinit parser and
> implementation support the same repoinit language version there is currently
> no way to express for a repoinit script which language version it minimally
> requires.
> This has been discussed in
> https://lists.apache.org/thread.html/r7eacbe10217fe0b4c0cfdbef3674b3438a9e7bc7feb71711f116145d%40%3Cdev.sling.apache.org%3E
> and the proposal is to allow the statement to appear multiple times in a
> (merged) repoinit script as different sections might have different
> requirements.
> When the parser tries to process a repoinit in a language version which is
> newer than the supported one a meaningful warning should be emitted and the
> processing should be skipped.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
