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

Upstream dependencies are incorrectly determined

XMLWordPrintable

      Consider this scenario:

      • Maven project A contains two modules, A1 (a jar) and A2 (a war), both of which declare A as their parent.
      • A's POM lists A1 and A2 in the <dependencyManagement> section.
      • A2's POM declares a dependency on A1.
      • Maven project B contains two modules, B1 (a jar) and B2 (a war), both of which declare B as their parent.
      • B's POM lists B1, B2, and A1 in the <dependencyManagement> section.
      • B2's POM declares a dependency on A1, but not A2.

      The problem:

      Jenkins lists A2 as an upstream project of B2, when the build option "Build whenever a SNAPSHOT dependency is built" is checked, which causes B2 to be built when changes are made to A2, but there are no explicit or transitive dependencies between A2 and B2.

          [JENKINS-21888] Upstream dependencies are incorrectly determined

          Jesse Glick added a comment -

          Surely this is the wrong component and should have been filed against maven-plugin?

          Jesse Glick added a comment - Surely this is the wrong component and should have been filed against maven-plugin ?

            Unassigned Unassigned
            exsortis Paul Schifferer
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: