[
https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695926#comment-15695926
]
Robert Munteanu commented on SLING-6332:
----------------------------------------
I've tried to debug with no luck. It seems that configurations should be merged
properly at the model level, since there are working tests for it. I think the
issue is at the Maven plug-in level. I've also attached a patchset to
SLING-6330 which applies on Sling trunk and reproduces the issue.
> Configurations from slingstart dependencies are not overwritten or merged
> -------------------------------------------------------------------------
>
> Key: SLING-6332
> URL: https://issues.apache.org/jira/browse/SLING-6332
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
> Reporter: Robert Munteanu
> Fix For: Slingstart Maven Plugin 1.7.0
>
>
> I have a 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)
