[
https://issues.apache.org/jira/browse/SLING-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903041#comment-16903041
]
Dominik Süß commented on SLING-8623:
------------------------------------
I noticed the edge case of a container package that doesn't contain own content
but is a wrapper for other packages. In contrast to prior practices - as those
are of type CONTENT this might require adjusting dependencies that were set on
those to the concrete subpackages. That does make sense anyhow as if the
subpackages contain both content and application packages a dependency to the
parent might resolve "too early" if the dependency is relying on the content
packages to be deployed. so Skipping those containers as well makes sense and
enforcing adjusting corresponding dependencies.
> Add support to cpConverter to drop content-packages of PackageType.CONTENT
> from targetmodel
> -------------------------------------------------------------------------------------------
>
> Key: SLING-8623
> URL: https://issues.apache.org/jira/browse/SLING-8623
> Project: Sling
> Issue Type: New Feature
> Components: Content-Package to Feature Model Converter
> Reporter: Dominik Süß
> Priority: Major
>
> In cases where content packages are converted for scenarios with use of
> CompositeNodeStore to handle the immutable content the featureModels are
> supposed to only install the immutable part of the repository - therefore the
> content-packages of PackageType.Content should be droppable. They anyhow
> can't be omitted from scanning & parsing as the conversion of service users,
> CNDs etc. into repoinit is still supposed to happen.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
