Le samedi 10 novembre 2012 19:15:47 Karl Heinz Marbaise a écrit :
> Hi Hervè,
>
> many for the explanation...
>
> > yes, the behaviour is known - probably not from many people, but I do
>
> know it
>
> > was a consequence of maven-dependency-tree-2.0 MSHARED-167
> >
> > I wouldn't say "intent
Hi Hervè,
many for the explanation...
> yes, the behaviour is known - probably not from many people, but I do
know it
was a consequence of maven-dependency-tree-2.0 MSHARED-167
I wouldn't say "intentional", but that's a consequence of using Aether in
Maven 3 instead of tracking internal Maven
yes, the behaviour is known - probably not from many people, but I do know it
was a consequence of maven-dependency-tree-2.0 MSHARED-167
I wouldn't say "intentional", but that's a consequence of using Aether in
Maven 3 instead of tracking internal Maven 2 dependency resolution events.
Maven 3/A
Hi,
i've played around with the maven-dependency-plugin to see which
artifacts are in my project via:
mvn dependency:tree -Dverbose=true
which results into the following output:
.
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
first-project ---
[INFO] com.soebes.tra
