Ben's suggestion should be enough.
dependency:analyze will output declared, unused dependencies and undeclared,
used dependencies (what you want)
Mind you, I've had quite a few false positives in the first category. I think
things like reflection will fool the analysis. But since you are intere
I've wondered this myself for a while as well. Hope you find an answer
-Original Message-
From: Sander Verhagen [mailto:san...@sanderverhagen.net]
Sent: Thursday, April 16, 2015 02:20 AM
To: users@maven.apache.org
Subject: Logging for dependencies of Maven plugin
Hi group,
I already
as
in a
multi-module project. As far as I see- maven-graph-plugin generates a graph per
module. Am I mistaken?
-Original Message-
From: Endo Alejandro [mailto:alejandro.e...@grassvalley.com]
Sent: 08 April 2015 17:33
To: Maven Users List
Subject: RE: Looking for a way to visualize depen
If by module granularity you mean excluding/including certain modules, check
this pull request I did on the maven-graph-plugin that has never been and
probably will never be merged to the main line (Ah the beauty of opensource,
you scratch your own itch and contribute it to the community but nob
Hello everyone
I thought I knew how maven did dependency conflict resolution: always go with
the version that's closest to the base pom
However, it seems that is not the case. Here is my scenario
I have a pom of packaging=pom, call it A, which is the base where I execute
maven.
So this is my
