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

      I have the following maven2 project hierarchy:

      -> A <-
       
       

      B <------ C

      So there is no circular dependency. This works nicely unless, C is a module of
      A, i.e.:
      a/pom.xml
      a/c/pom.xml
      b/pom.xml

      and A lists C as module.

      In Hudson, project A has B listed as both upstream and downstrean dependency,
      which results in an infinite build loop. However, I think this is a legal setup
      in Maven2, as there is no circular dependency. I haven't investigated this
      thoroughly, but it might be that modules are considered downstream projects even
      they aren't.

      I'll attach a test project demonstrating the bug. Just adding A and B to Hudson
      should cause the loop. If not, committing something should do it.

          [JENKINS-1722] Detect a cycle in Maven project and report it

          syvalta created issue -
          Kohsuke Kawaguchi made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          kutzi made changes -
          Link New: This issue is related to JENKINS-1714 [ JENKINS-1714 ]
          kutzi made changes -
          Priority Original: Critical [ 2 ] New: Major [ 3 ]
          Jenkins IRC Bot made changes -
          Component/s New: maven-plugin [ 16033 ]
          Component/s Original: maven2 [ 15487 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 131795 ] New: JNJira + In-Review [ 185301 ]

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

              Created:
              Updated: