[
https://issues.apache.org/jira/browse/JCRVLT-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086679#comment-16086679
]
Tobias Bocanegra commented on JCRVLT-195:
-----------------------------------------
in JCRVLT-32, we informally introduced the {{Import-Package}} manifest
property, which is exactly what you need. similar to OSGi bundles, it declares
the java package dependnecies of the package. for example if the package
contains JSPs, you can express the runtime dependencies through this property.
currently the property is not enforced or formally recognized trough the vault
API, so this issue is a good followup for this.
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.
> Support OSGi bundle dependencies
> --------------------------------
>
> Key: JCRVLT-195
> URL: https://issues.apache.org/jira/browse/JCRVLT-195
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Konrad Windszus
>
> 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)
