According to the maven 3 release notes
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html it's not
reliable.

"Furthermore, not all parts of the Maven 2.x resolution API could be bridged
onto Aether. Most notably the maven-dependency-tree shared component which
is used for mvn dependency:tree still uses the legacy resolution code. As
such, the output from mvn dependency:tree can differ from the actual
dependency tree used by Maven itself to derive the classpaths of a project.
For now, the actual dependency trees can be inspected when running Maven
with debug logging enabled."

Thanks for the hint though.

--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-3-provided-dependency-pulls-a-compile-dependency-tp4421451p4421584.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to