I'm trying to find out where the dependencies are coming from for a particular plugin goal. I know the dependencies exist because Maven downloaded them when I ran the goal for the first time. And they're not (directly) dependencies of my project, because I ran mvn clean install
first, and these dependencies weren't downloaded then.
In this specific case, I'm trying to figure out what the dependencies are when I run mvn sonar:sonar
, but I expect the answer will be general purpose. For instance, even though I've built this project a number of times, when I ran that goal Maven downloaded a bunch of new jars like maven-antrun-plugin.
Here are things I've tried:
mvn dependency:tree
shows the dependencies for the project, but not for the plugin goal (it doesn't include anything related to SonarQube in the list).mvn org.apache.maven.plugins:maven-help-plugin:3.2.0:effective-pom -Dverbose=true
also doesn't include anything related to SonarQube.mvn -X sonar:sonar
prints out what looks like a dependency graph, but it's missing the jars that Maven downloaded the first time I ran thesonar:sonar
goal.mvn -X dependency:resolve-plugins
seems to be meant to download the dependencies of plugins, but does not capture thesonar:sonar
dependencies. If I clear out my Maven cache, runmvn dependency:resolve-plugins
, and then runmvn sonar:sonar
, Maven has to download jars.