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

Inefficient build order for Maven2 projects


    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: maven-plugin
    • Labels:
    • Environment:
      Platform: All, OS: All
    • Similar Issues:


      We're using Maven 2 to build our modules. I've created the projects in
      Hudson and set a build trigger to build whenever a SNAPSHOT dependency
      is built. Unfortunately, it doesn't appear to do this in a
      breadth-first dependency order.


      All of our projects bar one have as a parent our company wide pom,
      which defines repositories, profiles, etc.

      If this project is built, it kicks of a build for the world, but lots
      of them are built repeatedly.

      e.g. Project Common contains our common POM.

      Project Alpha depends on Project Gamma and Project Common.
      Project Gamma depends on Project Common only.

      If Project Common gets built, Project Alpha seems to get built next
      (due to alphabetic ordering somewhere?), then Project Gamma is built,
      and the Project Alpha is built again, since Project Gamma has just
      been built.

      When we have 20 projects, this gets a little inefficient, with certain
      projects being built 3 or 4 times when they really only should be
      built once.


        1. maven-plugin.hpi
          2.20 MB
        2. patch.txt
          19 kB
        3. patch.txt
          18 kB
        4. patch V1.2.diff
          14 kB
        5. patch V1.3.diff
          20 kB

          Issue Links



              • Assignee:
                abayer Andrew Bayer
                jabley jabley
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: