[
https://issues.apache.org/jira/browse/JCRVLT-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138914#comment-17138914
]
Tobias Bocanegra edited comment on JCRVLT-443 at 6/18/20, 12:18 AM:
--------------------------------------------------------------------
I think we added the import package requirements for bundles to the package,
but never implemented a validation check. since jackrabbit doesn't really know
about OSGi.
But I agree with [~dsuess] that we should not allow dependencies in container
packages.
We use to do this for a long time, and it got us in deep troubles when trying
to resolve the installation order of larger package sets.
was (Author: tripod):
I think we added the import package requirements for bundles to the package,
but never implemented a validation check. since jackrabbit doesn't really know
about OSGi.
> Allow dependencies in "container" package type
> ----------------------------------------------
>
> Key: JCRVLT-443
> URL: https://issues.apache.org/jira/browse/JCRVLT-443
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 3.4.4
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: 3.4.6
>
>
> According to JCRVLT-170 {{container}} packages must not have package
> dependencies.
> Sometimes there are multiple container packages though and with the nesting
> of container packages added in JCRVLT-401 it makes sense now to add package
> dependencies also to containers (to enforce a certain order in case they are
> nested or just because at build time the dependency cannot be resolved, i.e.
> included in the container package)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
