[MDEP-282] Incorrect result with dependency:analyze for multi-module project

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 2.1
• Component/s: analyze
• Environment: MacOS 10.6.4; Mac Java 1.6.0
• Assignee: Unassigned
• Reporter: Anders Hammar
• Created: 27/Aug/10 06:21
• Updated: 12/Jan/16 20:12
• Resolved: 12/Jan/16 20:12

Description

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.

Issue Links

• is duplicated by: MDEP-367 'Unused declared dependencies found' incorrect with Maven 3.