maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Hammar (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MDEP-282) Incorrect result with dependency:analyze for multi-module project
Date Fri, 27 Aug 2010 12:32:32 GMT

    [ http://jira.codehaus.org/browse/MDEP-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233315#action_233315
] 

Anders Hammar commented on MDEP-282:
------------------------------------

Ok, so I should file this issue on the mave-dependency-plugin instead? Or can this one be
moved?

> Incorrect result with dependency:analyze for multi-module project
> -----------------------------------------------------------------
>
>                 Key: MDEP-282
>                 URL: http://jira.codehaus.org/browse/MDEP-282
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: MacOS 10.6.4
> Mac Java 1.6.0
>            Reporter: Anders Hammar
>         Attachments: depanalyze-bug.zip
>
>
> I found this regression in Maven 3.0-beta-2 compared to Maven 2.2.1:
> For the attached project, execute
> mvn dependency:analyze
> in the aggregating project.
> This will (incorrectly) report a dependency problem for module2, when executed with Maven
3.0-beta-2. With Maven 2.2.1, no problems is reported (which is correct).
> If executing the analyze in the module2 project with Maven 3.0-beta-2, no problem is
reported however.

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