On Thu, Mar 25, 2010 at 4:59 AM, Geronimo M. H. <[email protected]>wrote:
> Whow, > > you're my hero :) > > On Wednesday 24 March 2010 21:12:17, Andrew Schetinin wrote: > > Therefore I'm running it with the following command line switch: > > -Divy.cache.ttl.default=eternal > > The new timings: > > gradle: Prj-1 0:20 min 0:20 min > Prj-2 0:25 min 0:10 min > Prj-3 5:10 min 0:36 min > > That's great and for me, the result is that good, that I don't want to > spent > further efforts on optimization. The build-time is stil two times the time > of > ant, but I can live with that! > I'm not sure what the main reason for that is. There is always the Groovy startup time (the Groovy team is working on making this faster). For a clean build you also pay for collecting the incremental build information. But in regard to the average build time that usually pays of very well. And I'm sure there are some other areas where we can optimize the execution behavior of Gradle. Yet our main focus is to get the _average_ build time for enterprise builds down. > I would like to move that commandline parameter to a configuration setting > (some day), so that I don't have to use a wrapper script but can select the > remote lookup by use of different tasks. > Gradle should provide some DSL elements to express that. Would you mind filing a Jira for this with fix for 1.0? - Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleorg CEO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz > > kind regards > > Geronimo > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
