[
https://issues.apache.org/jira/browse/SLING-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369237#comment-17369237
]
Carsten Ziegeler commented on SLING-10538:
------------------------------------------
Yes, this is a change in behaviour which is disabled by default. If you enable
it, you opt-in to the new behaviour.
There might be different use cases. The use case this is about is to make
application configuration easier and avoid that an application configuration
needs to repeat each and every property from the platform. With this you can
get to a similar functionality as you have with feature models where
configurations are merged in the same way.
I'm not aware of use cases for a per configuration handling - there might; but
this would then be a different / new functionality.
> 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)
