You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/08/27 14:00:32 UTC
[jira] Moved: (MDEP-282) Incorrect result with dependency:analyze
for multi-module project
[ http://jira.codehaus.org/browse/MDEP-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-4784 to MDEP-282:
---------------------------------------------
Complexity: (was: Intermediate)
Affects Version/s: (was: 3.0-beta-2)
2.1
Key: MDEP-282 (was: MNG-4784)
Project: Maven 2.x Dependency Plugin (was: Maven 2 & 3)
> 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