[
https://issues.apache.org/jira/browse/JCRVLT-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138534#comment-17138534
]
Dominik Süß commented on JCRVLT-443:
------------------------------------
[~kwin] I don't know if I really can follow the scenario. The reasoning behind
containers not having dependencies is that the dependencies always relate to
content - so the dependency should be defined on the package within the
container holding the content it depends on. This is similar to not depending
on bundles but on java packages in osgi. We did even check if we could have
dependency vectors related to the actual content but that turned out to make
the dependency syntax far too complex - dependencies on the actual holding
content-package seems the most accurate way and avoids transient dependencies.
> 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)
