You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/01/27 16:46:00 UTC

[jira] [Commented] (SLING-9031) Support OR logic for run mode support

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

Konrad Windszus commented on SLING-9031:
----------------------------------------

Actually "|" is not a valid character for node names (https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.4%20Exposing%20Non-JCR%20Names) nor in most file systems, therefore using something like "," instead is probably more reasonable.

> Support OR logic for run mode support
> -------------------------------------
>
>                 Key: SLING-9031
>                 URL: https://issues.apache.org/jira/browse/SLING-9031
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>    Affects Versions: File Installer 1.1.0, JCR Installer 3.1.26
>            Reporter: Konrad Windszus
>            Priority: Major
>
> It would be nice if the run mode support in both the JCR installer (https://sling.apache.org/documentation/bundles/jcr-installer-provider.html#runmode-support) as well as the File installer (https://sling.apache.org/documentation/bundles/file-installer-provider.html#runmode-support) would be enhanced so that apart from the AND logic (with ".", requiring all run modes to be active) also an OR logic would be supported (i.e. to set a certain config on an instance having runmode a or b) without being forced to duplicate that config.
> As a syntax one could choose to use "|" as OR separator and keep using "." as AND separator (similar to the syntax of https://sling.apache.org/documentation/bundles/sling-settings-org-apache-sling-settings.html#defining-valid-run-modes). OR should have lower precedence so that AND is processed first.



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