[GRADLE-1714] Remote repositories hit on every build despite cache causing significant performance degradation Created: 03/Aug/11 Updated: 04/Jan/13 Resolved: 16/Oct/11 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.0-milestone-4 |
Fix Version/s: | 1.0-milestone-5 |
Type: | Bug | ||
Reporter: | Doug Lethin | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 1 |
Issue Links: |
|
Description |
I have a build with A LOT of dependencies (and transient dependencies), and discovered when I upgraded to milestone-4 that my builds went from 12 seconds to 2 minutes. I discovered this is due to the fact that for each dependency, it's remote repository is hit to get the pom file and the two checksum files. And to make matters worse, sometimes the jar files are re-downloaded. These are release version dependencies, not SNAPSHOTS. I marked it as major, but it seems pretty critical given the dramatic performance degradation. Please let me know if any sample or extra info is needed. Thanks. |
Comments |
Comment by Magnus Rundberget [ 03/Aug/11 ] |
Looks like a duplicate of http://issues.gradle.org/browse/GRADLE-1697 |
Comment by Adam Murdoch [ 12/Oct/11 ] |
This should be fixed. Can you try a recent milestone 5 snapshot out with your build? |