Hey Russel We value your feedback. A recent announcement http://forums.gradle.org/gradle/topics/on_our_way_to_gradle_1_0 explains pretty clearly our plan to first make dependency resolution work, then make it performant. Naturally, downloading the same artifact multiple times will not be considered performant, even across multiple versions of Gradle.
So rest assured we don't consider the current situation acceptable, except as a helpful stepping stone toward a final solution. One issue that we are dealing along the way is a mechanism to make every snapshot version of gradle work, without needing to be backward compatible with the cache layout of every previous snapshot version. Hope this helps explain the current situation. cheers Daz On 30 September 2011 10:37, Russel Winder <[email protected]> wrote: > Isn't there something wrong with a system that over and over again > downloads the same dependency from the Internet? The whole point of a > cache is that everything uses it to avoid accessing the Internet. > > Gradle has had a history of downloading the same dependency multiple > times for each phase of a build. Now we have that Gradle is encoding > its own version as part of the signature of a dependency. This seems > fundamentally wrong to me, but perhaps I am uneducated and thick as to > why a dependency that has no relationship to Gradle has to be treated as > being dependent on it? > > -- > Russel. > ============================================================================= > Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] > 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
