[
https://issues.apache.org/jira/browse/SLING-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756487#comment-16756487
]
Dominik Süß commented on SLING-8251:
------------------------------------
[~bosschaert],[~rombert] as [~kwin] noted some support was added via JCRVLT-32.
There yet is no full reflection of a capability and requirement model. The
content-package to content-package dependencies are in place since a long time
and even if they are considered an antipattern in the osgi space now it is out
in the wild and there is at least tooling around to help to identify hierarchic
dependencies. There were discussions around adding support for more generic
capability headers but this was not followed up on as first, we need to make
sure that we have an end-to-end tooling chain making use of the existing
metadata to understand the potential and benefit of further additions to the
vault metadata.
> Support checking dependencies for content packages
> --------------------------------------------------
>
> Key: SLING-8251
> URL: https://issues.apache.org/jira/browse/SLING-8251
> Project: Sling
> Issue Type: New Feature
> Components: Feature Model
> Reporter: Robert Munteanu
> Assignee: David Bosschaert
> Priority: Major
>
> When including content packages in a feature model there are some
> dependencies that would be great to check at build time. Both of these are
> defined as manifest headers:
> # dependencies to other content pacakges - Content-Package-Dependencies
> # dependencies to java packages - Import-Package (with the same syntax as the
> OSGi bundle Import-Package header ).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
