[GRADLE-1675] slow dependency resolution for certain snapshot dependencies Created: 15/Jul/11 Updated: 04/Jan/13 Resolved: 15/Jul/11 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | 1.0-milestone-4 |
Type: | Bug | ||
Reporter: | Szczepan Faber | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Description |
See ticket: http://support.gradleware.com/tickets/1023 git clone --recursive git://git.springsource.org/spring-integration/spring-integration.git Run again and see the resolution time: Edit build.gradle in the project root and change springVersion = '3.0.5.RELEASE' ./gradlew dependencies And find out why it is much slower. The debug log shows a lot of messages like: [org.gradle.api.internal.artifacts.ivyservice.IvyLoggingAdaper]found module in cache but with a different resolver: discarding: org.springframework#spring-expression;3.1.0.BUILD-SNAPSHOT; expected resolver=http://maven.springframework.org/snapshot; resolver=clientModuleChain So it looks like our ivy-related code (or ivy) is not using the cache eagerly enough. |
Comments |
Comment by Szczepan Faber [ 15/Jul/11 ] |
It seems the problem was fixed - I browsed through the commits and I think Adam resolved it while working on ivy services. Basically, with latest master, the resolve times are fairly fast regardless for the springVersion. milestone-3 & '3.1.0.BUILD-SNAPSHOT' : gradle dependencies takes ~ 4 mins |
Comment by Chris Beams [ 16/Jul/11 ] |
Quite glad to hear this is improving, but even at ~1 min... doesn't that seem like a long time just to resolve/report the dependency graph? |
Comment by Szczepan Faber [ 23/Jul/11 ] |
Possibly The resolution may still be slower occasionally, e.g. when snapshots are refreshed, version ranges resolved, etc. However, I'm with you - it should be quick. |