[
https://issues.apache.org/jira/browse/SLING-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Süß updated SLING-8215:
-------------------------------
Fix Version/s: Feature Model Content Extension 1.0.0
> Content-Extension fails to handle multilayer nesting of packages
> ----------------------------------------------------------------
>
> Key: SLING-8215
> URL: https://issues.apache.org/jira/browse/SLING-8215
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Reporter: Dominik Süß
> Assignee: Dominik Süß
> Priority: Major
> Fix For: Feature Model Content Extension 1.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As ExecutionPlan building requires adding all artifacts that are not
> explicitly referred as an inner dependency the ContentHandler has code to add
> also subpackages to the execution plan - this logic currently only walks into
> the first layer of nesting and doesn't address the option to have mutliple
> levels of nesting. This is a scenarios not really intended for use in with
> feature models - but since legacy structures need to be supported as well
> this leads to problems in scenarios of wrapperpackages for libraries (1 level
> of nesting) are embedded in container packages for the own application (2nd
> level of nesting)
> The symptom currently is to have the second level only registered and not
> installed unless there is an explicit dependency defined in another package.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
