-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: All
I have the following maven2 project hierarchy:
- |
B <------ C
So there is no circular dependency. This works nicely unless, C is a module of
A, i.e.:
a/pom.xml
a/c/pom.xml
b/pom.xml
and A lists C as module.
In Hudson, project A has B listed as both upstream and downstrean dependency,
which results in an infinite build loop. However, I think this is a legal setup
in Maven2, as there is no circular dependency. I haven't investigated this
thoroughly, but it might be that modules are considered downstream projects even
they aren't.
I'll attach a test project demonstrating the bug. Just adding A and B to Hudson
should cause the loop. If not, committing something should do it.
- is related to
-
JENKINS-1714 Disable automatic set upstream projects from maven dependencies
-
- Closed
-
[JENKINS-1722] Detect a cycle in Maven project and report it
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Link |
New:
This issue is related to |
Priority | Original: Critical [ 2 ] | New: Major [ 3 ] |
Component/s | New: maven-plugin [ 16033 ] | |
Component/s | Original: maven2 [ 15487 ] |
Workflow | Original: JNJira [ 131795 ] | New: JNJira + In-Review [ 185301 ] |