[
https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744624#comment-15744624
]
Julian Sedding commented on SLING-6332:
---------------------------------------
I think the expectation is that we can define multiple features in a single
maven module. IIUC different features can be activated using different
run-modes.
The use-case would be to have a "base" feature and then a variation/extension
of this feature, without requiring duplication of all the definitions. E.g. a
maven module might define a "launchpad" and a "testing" feature. The "testing"
feature would inherit all definitions from the "launchpad" feature, but add a
configuration property to a configuration and a few bundles to be installed.
Is that an accurate description of the use-case [~rombert]?
> 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)
