[MDEP-409] dependency:tree fails for a multi-module project where one module depends on another and "mvn install" has not been run yet

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 3.0.1
• Component/s: tree
• Environment: Linux
• Assignee: Michael Osipov
• Reporter: Eric Pabst
• Created: 08/May/13 13:23
• Updated: 16/May/17 14:32
• Resolved: 14/Apr/17 20:35

Description

When I run dependency:tree on a multi-module project without having run a "mvn install", it fails with this error:

[ERROR] Failed to execute goal on project slide-test-module-svn-2: Could not resolve dependencies for project org.slide:slide-test-module-svn-2:jar:1.1-SNAPSHOT: The following artifacts could not be resolved: org.slide:slide-test-module-svn-3:jar:1.1-SNAPSHOT, org.slide:git-component-for-testing-slide:jar:1.0.b1782: Could not find artifact org.slide:slide-test-module-svn-3:jar:1.1-SNAPSHOT in maven-central -> [Help 1]

Issue Links

• depends upon: MNG-4331 Add new requiresDependencyCollection mojo feature (with corresponding annotation) to grab dependency tree without files
• is related to: MDEP-568 dependency:go-offline -DexcludeGroupIds=xxxx still try to resolve artifacts in the excluded group xxxx
• is related to: MDEP-204 go-offline fails to resolve artifact available in maven reactor
• relates to: MNG-3283 Plugins that require dependency resolution in early phases cause dependency resolution issue
• links to: GitHub Pull Request #111