[
https://issues.apache.org/jira/browse/SLING-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755991#comment-16755991
]
Radu Cotescu commented on SLING-8251:
-------------------------------------
[~bosschaert], the Apache Sling Scripting Bundle Tracker (such a mouthful) [0]
doesn't work with content packages at all; instead it expects that bundles
providing {{sling.resourceType}} capabilities wire to it by explicitly
requesting the capability the tracker provides, and in return it registers
servlets for the exposed resource type capabilities. We haven't considered
adding support for working with scripts coming from content, since we'd really
want to actually get rid of this pattern.
[0] - https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker
> 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)
