[FIXED] maven: how to disable certain dependencies?

Issue

Well, I'm not talking about the well-known commons-logging problem, I know I can disable it by setting the 99.0-does-not-exist version.

My problems is, some packages are contained in different dependencies, say, aspectjlib is contained both in org.aspectj:aspectjlib and aspectj:aspectjlib. In some cases, transitive dependencies may introduce the two jars at the same time, while of different versions, e.g., org.aspectj:aspectjlib:1.7.3, aspectj:aspectjlib:1.6.1. And mis-loading aspectj:aspectjlib:1.6.1 accidentally is not my intention. So is there a way like commons-logging that I can disable aspectj:aspectjlib completely?

I tried the same trick using 99.0-does-not-exist, only to find an error from maven:

---

[ERROR] Failed to execute goal on project XXX: Could not resolve dependencies for project XXX:jar:1.0.0-SNAPSHOT: The following artifacts could not be resolved: aspectj:aspectjlib:jar:99.0-does-not-exist, aspectj:aspectjrt:jar:99.0-does-not-exist, aspectj:aspectjweaver:jar:99.0-does-not-exist: Could not find artifact aspectj:aspectjlib:jar:99.0-does-not-exist in tbmirror (http://mvnrepo.taobao.ali.com/mvn/repository) -> [Help 1]

Solution

Well, although some repositories do provide 99.0-does-not-exist for logging system dependencies like log4j, slf4j-log4j, commons-logging, etc., this is not a universal solution.

I find a solution to do this: use 'provided' scope. To clarify, in my example above, I have two conflicting dependencies: org.aspectj:aspectjlib:1.7.3, aspectj:aspectjlib:1.6.1, I want to disable aspectj:aspectjlib:1.6.1, I only need to put this in top-level pom:

<dependency>
    <groupId>aspectj</groupId>
    <artifactId>aspectjlib</artifactId>
    <version>1.6.1</version>
    <scope>provided</scope>
</dependency>

in this way, aspectj:aspectjlib:1.6.1 will never appear in the final built lib.

Answered By - Cody
Answer Checked By - Timothy Miller (JavaFixing Admin)