You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Rich Seddon (JIRA)" <ji...@codehaus.org> on 2013/03/21 16:40:52 UTC

[jira] (MNG-4999) Maven should fail the build or give a warning when there are cyclic dependencies

    [ https://jira.codehaus.org/browse/MNG-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322338#comment-322338 ] 

Rich Seddon commented on MNG-4999:
----------------------------------

I think it may be possible to close this now, this seems to do the job:  http://mojo.codehaus.org/extra-enforcer-rules/banCircularDependencies.html
                
> Maven should fail the build or give a warning when there are cyclic dependencies
> --------------------------------------------------------------------------------
>
>                 Key: MNG-4999
>                 URL: https://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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira