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 -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
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 using (from the effective pom) is below. I also tried using older versions of this plugin. Why is the order different for the same project and the same version of the dependency plugin? plugin artifactIdmaven-dependency-plugin/artifactId version2.8/version executions execution idbuild-classpath/id phasegenerate-sources/phase goals goalbuild-classpath/goal /goals configuration excludeScopeprovided/excludeScope prefix\/prefix pathSeparator;/pathSeparator outputFileclasspath.txt/outputFile useBaseVersiontrue/useBaseVersion /configuration /execution -- View this message in context: http://maven.40175.n5.nabble.com/dependency-build-classpath-returns-wrong-order-tp5773306.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
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 depends on A:1.0 and this dependency is provided. I tried to use the maven-enforcer-plugin to break the build of A in case there is a transitive dependency whose groupId and artifactId are the same as A, but it doesn't work because the dependency A:1.0 is provided. Any suggestions? -- View this message in context: http://maven.40175.n5.nabble.com/maven-enforcer-plugin-to-ban-a-transitive-provided-dependency-tp5752733.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
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: http://maven.40175.n5.nabble.com/maven-enforcer-plugin-to-ban-a-transitive-provided-dependency-tp5752733p5752745.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
