Am 12/16/16 um 17:25 schrieb Christian Schulte: > Am 12/16/16 um 15:21 schrieb Robert Scholte: >> >> but this cover the issue we are talking about, because IIUC you are saying >> that IF both junit and hamcrest get the test-scope AND hamcrest would have >> a dependency THEN that dependency is not added to the classpath. That is >> still unexpected behavior. > > Just add 'test' scope to the hamcrest dependency in that pom.
I am referring to the pom of my email. Just test with 'compile', 'runtime', 'test' and 'provided' scope in the management and repeat that with the 'optional' flag set to 'true' (mvn -X dependency:tree). For the 'test' and 'provided' scopes it is correct the dependency disappears. For 'compile' and 'runtime' scopes it is correct the dependency is resolved in 'runtime' and 'compile' scope. With 'optional' set to 'true' it is correct the dependency disappears. That's exactly the behaviour you could observe if all of this would have been declared directly with the dependency (without using any management). Dependency management in 3.4 makes the managed dependencies resolved the same way they would get resolved with all of what is done via the management would have been done directly on the dependencies without any management in use. Compare that to < 3.4. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
