You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 01:20:12 UTC

[jira] Moved: (MARTIFACT-21) Fail build on circular dependencies

     [ http://jira.codehaus.org/browse/MARTIFACT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved MNG-3370 to MARTIFACT-21:
--------------------------------------------

    Affects Version/s:     (was: 2.0.8)
          Component/s:     (was: Artifacts and Repositories)
             Workflow: jira  (was: Maven New)
                  Key: MARTIFACT-21  (was: MNG-3370)
              Project: Maven Artifact  (was: Maven 2)

> Fail build on circular dependencies
> -----------------------------------
>
>                 Key: MARTIFACT-21
>                 URL: http://jira.codehaus.org/browse/MARTIFACT-21
>             Project: Maven Artifact
>          Issue Type: Improvement
>            Reporter: Mark Hobson
>
> Currently circular dependencies are merely logged at debug level and not generally reported to the user.  The general consensus is that circular dependencies are bad, so I believe that they should be reported as early on as possible.  Previously the repository's low quality metadata was cited as a reason not to fail the build, but I would have thought such issues should have been rectified by now.
> Ideally we would throw a CyclicDependencyException in DefaultArtifactCollector.  If this is deemed too invasive, then we should at least increase the log level in DebugResolutionListener to warning.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira