[
https://jira.codehaus.org/browse/MDEP-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311931#comment-311931
]
Herve Boutemy commented on MDEP-282:
------------------------------------
I just tested and can reproduce
notice that {noformat}mvn install dependency:analyze{noformat} provides right
report
this seems to be related to the fact that package hasn't been done, then
dependency is still on a directory
Notice that Maven 2 build simply fails if you don't run install...
> Incorrect result with dependency:analyze for multi-module project
> -----------------------------------------------------------------
>
> Key: MDEP-282
> URL: https://jira.codehaus.org/browse/MDEP-282
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: analyze
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
