[jira] [Comment Edited] (SLING-2662) Enhance run mode handling

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

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

Bertrand Delacretaz edited comment on SLING-2662 at 7/26/16 12:04 PM:
----------------------------------------------------------------------

With the help of [~radu.cotescu] we have (finally) documented this at http://sling.staging.apache.org/documentation/bundles/sling-settings-org-apache-sling-settings.html , reviews and patches are welcome.


was (Author: bdelacretaz):
I have (finally) documented this at http://sling.staging.apache.org/documentation/bundles/sling-settings-org-apache-sling-settings.html , reviews and patches are welcome.

> Enhance run mode handling
> -------------------------
>
>                 Key: SLING-2662
>                 URL: https://issues.apache.org/jira/browse/SLING-2662
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Settings 1.1.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Settings 1.2.0
>
>
> Often there is a need to provide different features where the user might have the ability to choose whether a feature should be installed or not.
> This can easily be done with a run mode, so a feature is put into a run mode, and if the run mode is activated by the user, the feature is installed.
> However, there are cases where two features might be concurrent, so either feature A or feature B should be installed. Still run modes can be used by defining two run modes A and B - but in this case if the user does not choose one of the run modes, nothing is installed - or if the user selects both run modes, both are installed.
> We could support such use cases with some configuration properties for the settings service:
> a) we define a property which contains run modes that are usually always active
> b) in addition, we define a property which contains whether a run mode is active unless another run mode is active.
> So for the above use case, we define run mode A as always active and also set the second property to define that A is not active once B is activated by the user
> We could also define a third property which contains a set of run modes that are only choosable on the first startup of the installation, so in the in the example above, if this property is defined for A and B, the user selection of the first startup is preserved



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)