[
http://jira.codehaus.org/browse/MNG-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127113
]
Paul Benedict commented on MNG-3370:
------------------------------------
If A depends on B and B depends on A, I don't see why the build should fail.
You need both A and B on your classpath to compile. Circular dependencies can
be solved by putting in place holders (i.e., proxies) and then making a second
pass to clean them up. So I think the logging should switch from DEBUG to WARN,
but definitely be resolved.
> Fail build on circular dependencies
> -----------------------------------
>
> Key: MNG-3370
> URL: http://jira.codehaus.org/browse/MNG-3370
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.8
> 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
