[
https://issues.apache.org/jira/browse/SLING-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369310#comment-17369310
]
Carsten Ziegeler commented on SLING-10538:
------------------------------------------
One of the problems this tries to solve is the current gap between Sling
applications using launchpad and Sling applications using the feature model. If
you use the feature model and for example install features generated by the
content package converter, then the configurations will be merged. So if a
library is targeting a both systems it is behaving different today. This
feature closes the gap and aligns the launchpad behaviour with the feature
model one.
Also think about the situations where configurations evolve and new properties
are added to the platform. Without this feature, the values from the platform
configuration will not be applied, however the library does not know about it
either as it didn't exist when the library created the configuration.
And sure, documentation will follow
> 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)
