CODEWITHSUNDEEP
javaspringgradle
hublo
hublo

Reputation: 1180

Gradle getting newest version for some libraries

There is not any place in my project where I mentioned that I want to use any Spring library version 4.3.8.RELEASE. However, when doing an "assemble", Gradle picks up newest version for couple of dependencies. When I do a "gradle dependencies", I see:

+--- aopalliance:aopalliance:1.0
 |    |    +--- org.springframework.security:spring-security-core:3.2.0.RELEASE
 |    |    |    +--- aopalliance:aopalliance:1.0
 |    |    |    +--- org.springframework:spring-aop:3.2.6.RELEASE -> 4.3.8.RELEASE
 |    |    |    |    +--- org.springframework:spring-beans:4.3.8.RELEASE
 |    |    |    |    |    \--- org.springframework:spring-core:4.3.8.RELEASE
 |    |    |    |    |         \--- commons-logging:commons-logging:1.2
 |    |    |    |    \--- org.springframework:spring-core:4.3.8.RELEASE (*)
 |    |    |    +--- org.springframework:spring-beans:3.2.6.RELEASE -> 4.3.8.RELEASE (*)
 |    |    |    +--- org.springframework:spring-context:3.2.6.RELEASE -> 4.3.8.RELEASE
 |    |    |    |    +--- org.springframework:spring-aop:4.3.8.RELEASE (*)

Why the hell is Gradle doing something like : aop:3.2.6.RELEASE -> 4.3.8.RELEASE

Any other commands to track where a dependency come from?

Upvotes: 0

Views: 67

Answers (1)

LazerBanana
LazerBanana

Reputation: 7221

Those might be transitive dependencies coming from a different library.

Use dependencyInsight to track what comes from where.

gradle -q dependencyInsight --configuration <configuration> --dependency <dependency>

<dependency> - name of the dependency

<configuration> - compile, runtime etc.

You can also use dependencies and pipe it to the file and search for it manually.

gradle dependencies >deps.txt

Additional source gradle getting more dependency

Upvotes: 2

Related Questions