maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Régis Décamps (JIRA) <j...@codehaus.org>
Subject [jira] Commented: (MNG-3814) Reactor builds fail due to erroneous cycle in project sorting which does not consider versions
Date Sat, 29 Nov 2008 19:42:19 GMT

    [ http://jira.codehaus.org/browse/MNG-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155844#action_155844
] 

Régis Décamps commented on MNG-3814:
------------------------------------

The problem occurs with any type of dependency. It can be a plugin dependency or a dependency.
My project fails because
module-1.1 (uses plugin)-> plugin-1.0 (which depends on)-> module-1.0

> Reactor builds fail due to erroneous cycle in project sorting which does not consider
versions
> ----------------------------------------------------------------------------------------------
>
>                 Key: MNG-3814
>                 URL: http://jira.codehaus.org/browse/MNG-3814
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Reactor and workspace
>    Affects Versions: 2.0.9, 2.1.0-M1, 3.0-alpha-1
>            Reporter: Benjamin Bentmann
>
> Just to officially track the reason why the parent POM {{maven-plugins}} currently excludes
the maven-project-info-reports-plugin from the reactor:
> {noformat}
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] The projects in the reactor contain a cyclic reference:
> Edge between
>   'Vertex{label='org.apache.maven.plugins:maven-remote-resources-plugin'}'
> and
>   'Vertex{label='org.apache.maven.plugins:maven-project-info-reports-plugin'}'
> introduces to cycle in the graph
>   org.apache.maven.plugins:maven-project-info-reports-plugin -->
>   org.apache.maven.plugins:maven-remote-resources-plugin -->
>   org.apache.maven.plugins:maven-project-info-reports-plugin
> {noformat}
> It appears the {{ProjectSorter}} does not take versions into account, i.e. there is no
cycle in a multi-module scenario like this:
> {noformat}
> parent:1
> - plugin-a:2.0 which uses plugin-b:1.0
> - plugin-b:2.0 which uses plugin-a:1.0
> {noformat}

-- 
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

       

Mime
View raw message