Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8383

Maven Jobs should include their parent POM's fingerprint to correctly link projects


    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • maven-plugin
    • 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.

            paux Stephan Pauxberger
            paux Stephan Pauxberger
            1 Vote for this issue
            5 Start watching this issue