[jira] [Commented] (SLING-8168) Customer features should be able to tweak configs that were not enabled for tweaking

["Karl Pauls (JIRA)" <ji...@apache.org>]

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

Karl Pauls commented on SLING-8168:
-----------------------------------

I think this should somewhat work in the slingfeature merge case as there, the features should be comming in as specified and later features will override the previous ones in a merge. However, this might not be possible with the launcher as the launcher currently sorts the features. Maybe it shouldn't sort the features but rather merge them in the order they are given to the launcher.

> Customer features should be able to tweak configs that were not enabled for tweaking
> ------------------------------------------------------------------------------------
>
>                 Key: SLING-8168
>                 URL: https://issues.apache.org/jira/browse/SLING-8168
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>    Affects Versions: Feature Model Launcher 0.8.0
>            Reporter: Christian Schneider
>            Priority: Major
>             Fix For: Feature Model Launcher 0.8.2
>
>
> The feature model allows to change configs using variables. 
> Unfortunately only these predefined variables can be changed. So how do we handle when at feature creation a config definition does not contain a variable for tweaking the config but later a customer find he must tweak the config.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)