You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andreas Schaefer (Jira)" <ji...@apache.org> on 2021/02/23 23:03:00 UTC
[jira] [Commented] (SLING-10157) Converter fails with duplicate
configuration PIDs
[ https://issues.apache.org/jira/browse/SLING-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289419#comment-17289419 ]
Andreas Schaefer commented on SLING-10157:
------------------------------------------
The CP Converter has a mergeConfiguration flag that enables to deal with multiple configurations. That said I takes the configuration is order it finds it in the ZIP file and that is, I assume, alphabetically ordered.
I would prefer to have a way of setting a precedence based on the content-package but as far as I can tell this is not available to the FeaturesManager so I guess we should have something along the lines of the Sling Feature Model Plugin (USE_FIRST / USE_LATEST).
> 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)