Soare Alexandru
Soare Alexandru

Reputation: 11

Maven dependency exclusions not working as expected

I have the following situation:

Since A-updated and A are essentially the same library, but with different artifactId, I will get NoSuchField/Method errors because my project might reference the version from A, instead of A-updated.

I tried the following configuration in my main project's pom, but without any luck:

         <dependency>
            <groupId>com.test</groupId>
            <artifactId>B</artifactId>
            <version>1.00.01.0</version>
            <exclusions>
                <exclusion>
                    <groupId>com.test/groupId>
                    <artifactId>A</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

When running mvn:dependency tree I can still see the A library there. Do you have any thoughts?

Upvotes: 0

Views: 27

Answers (0)

Related Questions