You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2017/05/02 14:26:04 UTC

[jira] [Updated] (SLING-6332) Configurations with same PID but different features/run modes in provisioning model are ignored

     [ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated SLING-6332:
------------------------------------
    Fix Version/s:     (was: Sling Provisioning Model 1.8.2)
                   Sling Provisioning Model 1.8.4

> 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.4
>
>
> 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.15#6346)