[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743121#comment-15743121 ]
Robert Munteanu commented on SLING-6332: ---------------------------------------- My expectation - and I think [~chetanm] was also suprised by this - is that config merging 'just works'. If you feel strongly that merging configuration is a no-go, let's at least add a warning that a configuration merge/overwrite is not going to work as expected if we find the same configuration PID ( non-factory ) across different features. > Configurations with same PID but different features/run modes in provisioning > model are ignored > ------------------------------------------------------------------------------------------------ > > Key: SLING-6332 > URL: https://issues.apache.org/jira/browse/SLING-6332 > Project: Sling > Issue Type: Bug > Components: Tooling > Reporter: Robert Munteanu > Fix For: Sling Provisioning Model 1.8.0 > > > I have the following scenario: > # {{launchpad/builder}} defines an OSGi config for > {{org.apache.sling.jcr.base.internal.LoginAdminWhitelist}}, setting the > {{whitelist.bundles.additional}} property > # {{launchpad/testing}} depends on {{launchpad/builder}} and defines an the > same config with {{[mode=merge]}} and sets the {{whitelist.bundles.regexp}} > property > When building {{launchpad/testing}}, the configuration from this project is > ignored completely and the one from {{launchpad/builder}} is picked up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)