[
https://issues.apache.org/jira/browse/JCRVLT-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087010#comment-16087010
]
Konrad Windszus commented on JCRVLT-195:
----------------------------------------
{quote}
btw: Adobe's content-package-maven-plugin supports class analysis of content
packages and computes the import-package automatically; together with sling's
JSPC plugin, this is very convenient.
{quote}
Which version of the c-p-m-p supports this? The latest version 0.5.1 being
exposed at
https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/
does not seem to generate those headers.
> Support OSGi bundle dependencies
> --------------------------------
>
> Key: JCRVLT-195
> URL: https://issues.apache.org/jira/browse/JCRVLT-195
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Reporter: Konrad Windszus
> Assignee: Tobias Bocanegra
> Fix For: 3.1.42
>
>
> FileVault Packages support both internal and external hooks. Internal hooks
> are JARs which are part of the package itself. External hooks are provided
> through some classloader (usually through the Bundle Classloader in an OSGi
> context, https://issues.apache.org/jira/browse/JCRVLT-116). Installing a
> package depending on an external hook class which is not found, leads to an
> error.
> Therefore it would be beneficial to explicitly add a dependency from the
> package referencing an external hook towards the OSGi bundle providing the
> hook. Only that way it can be assured, that the installation of this package
> is deferred until that bundle providing the hook is finally active. Currently
> only package dependencies are supported though, which are not enough, as
> there is a delay until the embedded bundle in a package is deployed as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
