Hi,
If you run maven dependency:tree, which version of the
maven-dependency-plugin do you see?
(Look for something like:
[INFO] --- maven-dependency-plugin:3.1.2:tree (default-cli) @ your-module
)
And if it is something other than 3.1.2:
* Why aren't you using the latest version?
* Why don't
Hi, thank you for the responses.
Currently I was trying on a multi-module project, and
mvn dependency:tree
fails complaining about the impossibility to find artifact for one of the
reactor modules, but
mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:tree
works. I've tried
That was not a workaround, but me trying to reproduce the problem. I wasn't
able to reproduce it.
All the artifacts in the reactor could be found without building them. Are
you maybe trying to only build one module instead of the reactor?
With regards,
Nick Stolwijk
~~~ Try to leave this world
Hello,
maybe the workaround indicated here will help you:
http://maven.40175.n5.nabble.com/Finding-SNAPSHOT-dependencies-without-compiling-first-td5998636.html#a5998639
But I'm not confident on the rasons why it works like this...
*- - - - -François Marot*
On Mon, 6 Jul 2020 at 23:16, Anton
Hello,
Can anyone explain why "mvn dependency:tree" fails if the project artifacts are
absent in ~/.m2?
Also, if I place an empty, dummy file in place of the artifact in ~/.m2
dependency:tree starts working.
This means the artifact content is not needed for that operation.
Can this be worked
