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 a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~ Lord Baden-Powell On Tue, Jul 7, 2020 at 9:17 PM Francois Marot <francois.ma...@gmail.com> wrote: > 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 Vodonosov <avodono...@yandex.ru> wrote: > > > 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 around somehow, to allow producing project dependency > > without building the project? > > > > Best regards, > > - Anton > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
