[
https://issues.apache.org/jira/browse/SLING-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290699#comment-17290699
]
Carsten Ziegeler commented on SLING-10157:
------------------------------------------
We need to have a consistent, repeatable solution - in the old world with the
OSGi installer, the way it works is:
- if all configurations are known, alphabetical ordering of the id is used, the
first being used (so /apps before /libs)
- if a configuration is already installed and a new one with the PID at a
different location arrives, the new one is not considered regardless of the path
So that already is inconsistent and depends on installation order; which is a
bad idea - we must not make the same mistake here again.
> 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)
