You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2016/11/25 14:39:58 UTC
[jira] [Updated] (SLING-6332) Slingstart plugin: configurations
from different features/run modes are silently discarded
[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz updated SLING-6332:
---------------------------------------
Summary: Slingstart plugin: configurations from different features/run modes are silently discarded (was: Configurations from different features are silently discarded)
> Slingstart plugin: configurations from different features/run modes are silently discarded
> ------------------------------------------------------------------------------------------
>
> 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 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)