Maven brings "test" transitive dependency as "compile"

Question

When I run "mvn dependency:tree" for my project it shows the following: ``` [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ xxxxx --- [INFO] com.xxx.xxx:xxxxx:war:3.1.0-SNAPSHOT ... [INFO] +- commons-configuration:commons-configuration:jar:1.5:compile [INFO] | \- commons-beanutils:commons-beanutils-core:jar:1.7.0:compile [INFO] +- org.seleniumhq.selenium:selenium-api:jar:2.34.0:test [INFO] | +- com.google.guava:guava:jar:14.0:test [INFO] | \- org.json:json:jar:20080701:test [INFO] +- org.seleniumhq.selenium:selenium-htmlunit-driver:jar:2.34.0:test [INFO] | +- org.seleniumhq.selenium:selenium-remote-driver:jar:2.34.0:test [INFO] | | +- cglib:cglib-nodep:jar:2.1_3:test [INFO] | | +- net.java.dev.jna:jna:jar:3.4.0:test [INFO] | | \- net.java.dev.jna:platform:jar:3.4.0:test [INFO] | \- net.sourceforge.htmlunit:htmlunit:jar:2.12:test [INFO] | +- org.apache.commons:commons-lang3:jar:3.1:test [INFO] | +- org.apache.httpcomponents:httpmime:jar:4.2.3:test [INFO] | +- net.sourceforg…

Accepted Answer

I had a similar problem.

In my case an entry in the dependencyManagement of a parent pom set the scope of the dependent artefact to compile. Actually I omitted the scope tag which effectively is the same as setting it to compile. Changing it to provided helped. Seems the scope in dependencyManagement takes precedence over the transitive scope. Which makes sense but can still cause confusion when all you wanted to do is define the version.

It was actually not hard to spot: Looking at the effective-pom showed the dependencyManagement entry.

Maven brings "test" transitive dependency as "compile"

Solution

Problem