[
https://issues.apache.org/jira/browse/JCRVLT-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087029#comment-16087029
]
Tobias Bocanegra commented on JCRVLT-195:
-----------------------------------------
bq. 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.
unfortunately the repo.adobe.com doesn't have the recent version. I'll check
how we can update it.
bq. Not sure this is the same use case, because most of the java classes being
used from JSPs are provided by a bundle embedded in the same package. I guess
for those (runtime) dependencies there is no need to list those in the package
manifest. Also external packages being referenced from JSPs are not technically
required to install the package.
"we" (AEM) tries to get away from package with mixed types, but create
individual packages that only contain application (scripts, jsps, etc), or
configuration, or bundles, etc. this way the dependencies can be enforced
stricter (in fact, we don't use package anymore to deploy the bundles, but
using provisioning profiles, but this is a different topic).
but maybe the "AEM integrator" use case is a bit different, as they might not
have the same requirements to keep bundles and scripts separate.
bq. The use case for hooks is a bit different, as the installation of the
package actually requires the dependent package to be there. So I am talking
about a installation time dependency and you about a runtime dependency. Not
sure whether both should use the same headers.
agreed. so we could add a "scope" parameter to the import-package, like:
{noformat}
import-package: my-hook-service;version=1.0;scope=installation
{noformat}
> 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)
