[
https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744335#comment-15744335
]
Carsten Ziegeler commented on SLING-6332:
-----------------------------------------
Well, what does "just works" mean?
Merging of configurations is there if you have a base feature and want to
extend it - that's exactly the launchpad/testing case. Launchpad defines the
base (or application feature), and testing adds additional stuff or adjust
configurations etc to a feature.
Maybe we have to update the documentation and make it clear, that merging only
works on a feature base, but other than that I think we should not do anything.
The same happens for bundles as well, if you have to features with the same
bundle, then each feature lists this bundle, there is no merging or removal etc.
> 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)
