Re: dependency build-classpath returns wrong order

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

dependency build-classpath returns wrong order

Hi, I am using the maven-dependency-plugin version 2.8. If I run mvn dependency:build-classpath for one of my project I get the correct order of the dependencies, but if I generate the classpath in the maven build itself of my project then the order is messed up. The plugin configuration I am

maven-enforcer-plugin to ban a transitive provided dependency

Hi, I have the following scenario: my project (A) has a number of compile dependencies on other internal projects (B0, B1, B2 ...). I would like to break the build of A in case Bx has been built depending on an older release of A. So for instance: A:2.0-SNAPSHOT depends on B3:2.3 and B3:2.3

Re: maven-enforcer-plugin to ban a transitive provided dependency

Thank you Stephen! Does anybody knows if there is already a plugin able to this? David PS: Guys don't publish unrelated posts on this thread. -- View this message in context: