You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/02/27 12:52:00 UTC
[jira] [Created] (JCRVLT-416) Adding a package dependency to a
package containing it as subpackage leads to a dependency cycle
Konrad Windszus created JCRVLT-416:
--------------------------------------
Summary: 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
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)