-
Improvement
-
Resolution: Fixed
-
Major
-
None
Given two Maven2 projects:
Project A (POM only)
Project B (Jar), has A as parent (build when SNAPSHOT-dependencies are built)
Now, when A is built (#1), a build of B (#1) is correctly triggered. A shows a DS dependency to B, B an US dependency to A.
However, when viewing build #1 of A, it shows a downstream dependency to B without a specific build number (none).
When comparing both projects via "project dependecies", no dependencies are shown, which is plainly wrong.
A small change to MavenFingerprinter should do the trick.
[JENKINS-8383] Maven Jobs should include their parent POM's fingerprint to correctly link projects
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Assignee | New: Stephan Pauxberger [ paux ] | |
Resolution | Original: Cannot Reproduce [ 5 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Assignee | Original: Stephan Pauxberger [ paux ] | New: kutzi [ kutzi ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Assignee | Original: kutzi [ kutzi ] | New: Stephan Pauxberger [ paux ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
Component/s | New: maven-plugin [ 16033 ] | |
Component/s | Original: maven2 [ 15487 ] |
Workflow | Original: JNJira [ 138493 ] | New: JNJira + In-Review [ 188023 ] |