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

"Use private Maven repository" sometimes prevents upstream/downstream resolution

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: Linux

      I have a bunch of Maven2 projects that depend on each other, each built separately
      by Hudson. Before we upgraded to 1.318 and selected "Use private Maven repository"
      for these projects, they correctly found their upstream/downstream dependencies
      and built in the right order. Now, a change to any one project only builds it.

      I have an aggregation project that runs (sonar, findbugs, pmd etc) on a top-level
      pom over all these projects, also with a private Maven repository, and it
      correctly identifies modules and kicks off dependent builds (although I'd rather
      it didn't!), so the fact that the sub-modules don't is a bit strange.

            Unassigned Unassigned
            agenticarus agenticarus
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: