[
https://issues.apache.org/jira/browse/SLING-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290504#comment-17290504
]
Andreas Schaefer commented on SLING-10157:
------------------------------------------
The issue I encounter is a little bit more delicate as it is forced by the way
Feature Models are handled.
Traditionally I would install (external) package into Sling that may contain
OSGi configurations (assume here it does).
Then I would install the client's custom project package which its custom
configuration which in turn overrides the default configuration of the external
package.
Because this happens at different times (two separate installation tasks) the
order is defined by that.
In the Feature Model world the customer might combine both packages into one
package (required by Skyline) together with the configurations and here we need
to provide a strategy to resolve it.
For now we can rely on an alphabetical order meaning that the overriding
configuration but that might getting ugly when the configuration is in the
/libs folder.
> Converter fails with duplicate configuration PIDs
> -------------------------------------------------
>
> Key: SLING-10157
> URL: https://issues.apache.org/jira/browse/SLING-10157
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Affects Versions: Content-Package to Feature Model Converter 1.0.24
> Reporter: Carsten Ziegeler
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.0.26
>
>
> If there is a configuration for the same PID multiple times, either in the
> same or different content packages, the converter fails with an error.
> We should handle this similar to how the OSGi installer does it, and pick the
> right configuration based on the repository path.
> A warning should be logged for these cases as well.
> We could add a strict option, throwing an exception in this case like today
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
