Skip to content

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

@jira-importer

Description

@jira-importer

Eric Pabst opened MDEP-409 and commented

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]

Affects: 2.7

Attachments:

Issue Links:

  • MDEP-204 go-offline fails to resolve artifact available in maven reactor

  • MDEP-568 dependency:go-offline -DexcludeGroupIds=xxxx still try to resolve artifacts in the excluded group xxxx

  • MNG-3283 Plugins that require dependency resolution in early phases cause dependency resolution issue

  • MNG-4331 Add new requiresDependencyCollection mojo feature (with corresponding annotation) to grab dependency tree without files
    ("depends upon")

Remote Links:

4 votes, 9 watchers

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingpriority:majorMajor loss of function

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions