[
https://issues.apache.org/jira/browse/SLING-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872312#comment-16872312
]
Simone Tripodi commented on SLING-8529:
---------------------------------------
an initial version is implemented in the
[avoid_subpackages_flattering|https://github.com/apache/sling-org-apache-sling-feature-cpconverter/tree/avoid_subpackages_flattering]
branch
> Avoid flattening of subpackages during convertion in featuremodel
> -----------------------------------------------------------------
>
> Key: SLING-8529
> URL: https://issues.apache.org/jira/browse/SLING-8529
> Project: Sling
> Issue Type: New Feature
> Components: Content-Package to Feature Model Converter
> Reporter: Simone Tripodi
> Assignee: Simone Tripodi
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During testing of various valid scenarios it became apparent that certain
> dependency scenarios for nested subpackages might start failing. If packages
> start to depend on each other or even deeper nested packages depend on each
> other we currently do not preserve the right order when flattening).
> Instead the subpackages should be extracted (like bundles) and the implicit
> dependency to the (converted) parent package be made explicit (add dependency
> if not already existing.
> The solution would mean:
> * subpackages are extracted from the package and no longer handled as
> subpackages
> * the subpackages get an additional explicit dependency on the parent
> package (that was previously implicitly present)
> * the feature model contains all the converted packages and subpackages
> instead of a flattened one
> * converted package and converted subpackages end up in the defined cache
> folder
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
