[GRADLE-1986] Milestone-6 dependency resolution keeps on going Created: 07/Dec/11 Updated: 04/Jan/13 Resolved: 05/Jan/12 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.0-milestone-6 |
| Fix Version/s: | 1.0-milestone-7 |
| Type: | Bug | ||
| Reporter: | Gradle Forums | Assignee: | Adam Murdoch |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
Hi Guys, Just tried out the new milestone-6 which Luke Daley pointed me to on Twitter. For at least one of our projects it keeps on going with the dependency resolution. It seems like it is continuously looping in the DependencyGraphBuilder. It might be that the dependencies we have together make up a cykel, which then makes it go round in circles. I have a 3.1M gzipped log for the interested on dropbox: [1]http://dl.dropbox.com/u/2619303/gradl... Regards, |
| Comments |
| Comment by Gradle Forums [ 07/Dec/11 ] |
|
Thanks for the report Jeroen. Will take a look at the log and see if we can work out whats going on. For the project in question, does `gradle dependencies` complete? |
| Comment by Gradle Forums [ 07/Dec/11 ] |
|
Thx Luke! gradle dependencies does not finish in a reasonable amount of time, ie I killed it after 10+ minutes. Both that and the build seem to be running insane once its doing the 'Resolving dependencies'. |
| Comment by Gradle Forums [ 07/Dec/11 ] |
|
I'm having the same problem. Seems to be limited to my testCompile and testRuntime dependencies for a specific project. I'm using a special `testFixtures` configuration that extends from `testRuntime` in order to accomplish project dependencies for unit test code in a multi-project build. So I define this: configurations { In order to do something like this: testCompile project(path: ":coreProject", configuration: "testFixtures") Not sure if this is related or not but seems relevant. For my setup, it seems there is a lot of conflict resolution taking place between different versions of modules that are direct dependencies vs transitive dependencies. 1.0-milestone-3 seems to handle it fine, but 1.0-milestone-6 does not. Haven't tested other releases. |
| Comment by Adam Murdoch [ 19/Dec/11 ] |
|
This should be fixed now. Could you try the 1.0-milestone-7 snapshot? See http://forums.gradle.org/gradle/topics/gradle_1_0_milestone_7_snapshot_available |