[ https://issues.apache.org/jira/browse/SLING-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161247#comment-17161247 ]
Robert Munteanu commented on SLING-9587: ---------------------------------------- [~dsuess] - the rules are SonarCloud defaults and it's up to each reviewer to say that it's ok (or not) for the code coverage gate to fail. > 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üß > Assignee: Karl Pauls > 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)