[
http://jira.codehaus.org/browse/MNG-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253539#action_253539
]
Brett Porter commented on MNG-4999:
-----------------------------------
There were real examples of this at the time that prevented this being the
initial behaviour (dom4j and jaxen comes to mind).
I can see it might be useful to enable this as an option, though. Looking
through JIRA, I can't see any other such request - all seem to be related to
strange behaviour when there are cycles.
> Maven should fail the build or give a warning when there are cyclic
> dependencies
> --------------------------------------------------------------------------------
>
> Key: MNG-4999
> URL: http://jira.codehaus.org/browse/MNG-4999
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
> Affects Versions: 2.2.1, 3.0.2
> Environment: any
> Reporter: Phillip Hellewell
>
> Maven gives no warning or error when there are cyclic dependencies. It
> should give at least a warning, and have the ability to fail the build
> through an option.
> How to reproduce:
> 1. Make B that doesn't depend on anything. Deploy a snapshot of B.
> 2. Make A that depends on the snapshot of B . Deploy a snapshot of A.
> 3. Change B to depend on the snapshot of A. Now deploy a new snapshot of B
> (same version as in step 1).
> I would venture to say that the perc. of people who actually want to allow
> cycles is smaller than the percentage who want to catch it as an error.
--
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
