[
https://issues.apache.org/jira/browse/SLING-8647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911764#comment-16911764
]
Carsten Ziegeler commented on SLING-8647:
-----------------------------------------
A collision should probably be handled on a PID level, so if two features have
the same PID we could introduce a global configuration merge policy:
- FAIL_ON_CLASH - fail the merge when there is a clash for a PID - this should
be the default
- FAIL_ON_PROPERTY_CLASH - fail the merge only when there is a clash on a
property level
- USE_LATEST - use the latest configuration, but don't merge
- MERGE_LATEST - merge the latest configuration in, latest props might override
previous values
MERGE_LATEST is the current default
Open questions:
* do we need a more fine grained control like defining the policy on a per PID
level?
* is there a need to define the configuration in the override, similar to
define the framework property level?
> Provide policies for configuration merging
> ------------------------------------------
>
> Key: SLING-8647
> URL: https://issues.apache.org/jira/browse/SLING-8647
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Reporter: Carsten Ziegeler
> Priority: Major
> Fix For: Feature Model 1.1.0
>
>
> At the moment, configurations are merged automatically with properties from
> the later feature potentially overwriting properties from an earlier feature.
> However for bundles/artifacts as well as framework properties we removed the
> auto merge and introduced policies.
> As automatic merging of configurations can be a source of error, we should
> introduce such policies for configurations as well
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
