[
https://issues.apache.org/jira/browse/SLING-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755388#comment-16755388
]
Robert Munteanu commented on SLING-8251:
----------------------------------------
[~bosschaert] - I guess for me the first step is to support what metadata is
actually provided by the content packages, since it's out there in the wild.
Supporting new formats depends on getting the tooling in the VLT tooling and
also in releasing those packages with updated tooling, which might be slow.
For the vlt part I think [~tripod] is the best to discuss this (and probably
[~dsuess] knows a lot ).
(Also [~cziegeler] and [~kpauls] are probably interested as well)
> 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)
