Description
The the sub-package extraction mechanism automatically adds the parent packages as dependency to the subpackages. this is important if the parent package contains content that is required by the subpackages, thus the former way created an implicit dependency.
if the parent package has no own content and is only used a container package, this dependency is not required and even might cause to problems in certain cases.
suggest:
- on subpackage extraction, check if the parent package specifies content in the filter
- if no content is specified, to create dependency
- if no content is specified, the package can every be marked as installed.
Attachments
Issue Links
- is related to
-
JCRVLT-416 Adding a package dependency to a package containing it as subpackage leads to a dependency cycle
-
- Resolved
-
- relates to
-
JCRVLT-140 Add support for extract subpackages without installing content
-
- Closed
-