[
https://issues.apache.org/jira/browse/SLING-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369261#comment-17369261
]
Konrad Windszus commented on SLING-10538:
-----------------------------------------
My concern is that the same configuration files/content packages behave
differently depending on the this flag. This is e.g. an issue for
libraries/implementations which target different platforms, e.g.
https://adobe-consulting-services.github.io/acs-aem-commons/index.html or
https://adobe-consulting-services.github.io/acs-aem-commons/index.html.
Those use cases would require an opt-in to this feature per configuration, WDYT?
In any case, if we stick with this feature flag we need to document it at
https://sling.apache.org/documentation/bundles/configuration-installer-factory.html
probably with some sentences around the former handling and priorities of
configurations...
> Support merging of configurations
> ---------------------------------
>
> Key: SLING-10538
> URL: https://issues.apache.org/jira/browse/SLING-10538
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Installer Core 3.11.6, Installer Configuration Factory
> 1.3.6
>
>
> Today, the installer support for configurations applies a configuration as a
> unit. While this is useful for many use cases, there are use cases where for
> example an application provides an ootb OSGi configuration and the
> customization of that configuration should only contain the changed
> properties but not repeat all properties from the application.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
