You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dominik Süß (Jira)" <ji...@apache.org> on 2020/07/13 21:00:03 UTC
[jira] [Commented] (SLING-9587) Content-packages ref not ordered by
dependencies for nested packages
[ https://issues.apache.org/jira/browse/SLING-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156974#comment-17156974 ]
Dominik Süß commented on SLING-9587:
------------------------------------
Created PR at https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/29
> Content-packages ref not ordered by dependencies for nested packages
> --------------------------------------------------------------------
>
> Key: SLING-9587
> URL: https://issues.apache.org/jira/browse/SLING-9587
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Affects Versions: Content-Package to Feature Model Converter 1.0.10
> Reporter: Dominik Süß
> Priority: Critical
> Fix For: Content-Package to Feature Model Converter 1.0.12
>
>
> The order logic of the cp converter currently only considers the highest level packages passed into the converter - installing the identified packages of type content based on the content-refs subsequently can fail if the packages as picked up by traversal are not in the order of their dependencies.
> As the order can be calculated via DependencyUtil the output just needs to be ordered after all entries have been calculated instead of passing to the writer right away.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)