[
https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741887#comment-15741887
]
Carsten Ziegeler commented on SLING-6332:
-----------------------------------------
A feature is a single deployment unit - I think we made the initial mistake to
allow several features in a single file - but that's a different issue.
So someone deploying a feature has no idea which other features are deployed
and in which order, so merged configurations is not really going to fly across
features.
For run modes, it's defined that the most specific run mode wins
> 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)
