[
https://issues.apache.org/jira/browse/JCRVLT-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138600#comment-17138600
]
Dominik Süß commented on JCRVLT-443:
------------------------------------
[~kwin] no that is exactly what we want to prevent - the analysers are supposed
to check the dependencies of the actual contained artifacts and not
dependencies between containers. The effective dependency that you are
describing is an import-package (java) dependency that should be formulated as
such, any additional dependency is a wrong constraint - it doesn't matter if
the java package is provided by container a or container b, it just matters
that the import-package requirement is being satisfied.
> 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)
