I have been able to understand where the issue is, but not how to solve it. The wrong classpath is generated when I use the configuration property "excludeScope=provided".
So if I run: mvn dependency:build-classpath I get the correct classpath, but if I run: mvn dependency:build-classpath -DexcludeScope=provided then the classpath has a weird order that doesn't correspond to the dependency tree. Is this a known bug of the dependency plugin? -- View this message in context: http://maven.40175.n5.nabble.com/dependency-build-classpath-returns-wrong-order-tp5773306p5773488.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
