Skip to content

[MDEP-830] Dependencies of explicit dependencies of plugins are not resolved #1335

@jira-importer

Description

@jira-importer

Donal Fellows opened MDEP-830 and commented

Context: I'm using Error Prone following the instructions here. That involves using an added dependency of the maven compile plugin (specifically com.google.errorprone:error_prone_core:2.15.0 but I don't believe that that detail is so critical), where that added dependency defines an additional static checker. That plugin to the maven compiler plugin itself has its own dependencies (protobuf and a few other things; their exact identity is unimportant I believe, other than that they're not otherwise dependencies of the project).

Problem: When I use {}mvn dependency:resolve-plugins{}, the dependencies of the error_prone_core maven module are not downloaded. This is rather noticeable in my continuous integration flows, where I'm using the resolve and resolve-plugins goals to ensure that network activity is minimised and only performed at the beginning of the workflow (to try to promote reliability).  I happen to only be defining these things in a profile, but that profile is activated at the point where the resolve-plugins goal is called.

What I want to see: resolve-plugins follow that particular rabbit hole as well, and find and download the dependencies of the dependencies of the plugin.


Affects: 3.3.0

Issue Links:

  • MDEP-507 dependency:resolve-plugins and dependency:go-offline doesn't respect plugin dependencies from pom.xml

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpriority:minorMinor loss of function, or other problem where easy workaround is present

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions