[
https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744400#comment-15744400
]
Carsten Ziegeler commented on SLING-6332:
-----------------------------------------
I thought that the slingstart maven plugin is already detecting this situation
and issuing an error if a configuration for the same pid is provided more than
once (from more than one feature).
If that is not the case, I totally agree that we should do so and detect/report
this at build time
> 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)
