[
https://issues.apache.org/jira/browse/JCRVLT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047314#comment-17047314
]
Tobias Bocanegra commented on JCRVLT-416:
-----------------------------------------
bq. But once you also add a as dependency to b you get a dependency cycle.
why should a be a dependency of b ? it's the other way around.
you can install 'b' without 'a', but not vice versa.
> Adding a package dependency to a package containing it as subpackage leads to
> a dependency cycle
> ------------------------------------------------------------------------------------------------
>
> Key: JCRVLT-416
> URL: https://issues.apache.org/jira/browse/JCRVLT-416
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
> Affects Versions: package-maven-plugin-1.1.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: package-maven-plugin-1.1.2
>
>
> Consider the case where {{a}} is a subpackage of {{b}}. This requires {{a}}
> being a Maven dependency of Maven Module {{b}}. Since every package
> installation of {{b}} adds {{b}} as package dependency to {{a}} implicitly
> (compare with https://issues.apache.org/jira/browse/JCRVLT-140) it should
> also be possible to make this implicit dependency and explicit one (to make
> the validator be able to detect e.g. filter roots being provided by {{b}}).
> But once you also add {{a}} as dependency to {{b}} you get a dependency cycle.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
