You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2018/11/19 19:12:00 UTC

[jira] [Resolved] (SLING-8119) Improve configuration handling

     [ https://issues.apache.org/jira/browse/SLING-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-8119.
-------------------------------------
    Resolution: Fixed

Implemented recording of the originating feature as well

> Improve configuration handling
> ------------------------------
>
>                 Key: SLING-8119
>                 URL: https://issues.apache.org/jira/browse/SLING-8119
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Blocker
>             Fix For: Feature Model 0.2.2, Feature Model IO 0.2.2, Feature Model Analyser 0.2.2, Feature Model Converter 0.2.2, Feature Model Launcher 0.2.2
>
>
> Handling of configurations needs some improvements:
> * We should record the origin feature when features are merged like we do for artifacts
> * The special properties like the origin from above and the bundle the configuration belongs to, should have a special prefix like ":feature:" (similar to what the configurator does)
> * We should add a method to configuration which gets all properties minus the special ones, this method can then be used by the launcher (or other tools) to set the configuration
> * We don't need to distinguish between a configuration and a factory configuration, both have a PID



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