Re: [gradle-user] Proper gradle daemon usage

2011-11-06 Thread Daz DeBoer
Hi Ed Can you give http://repo.gradle.org/gradle/distributions-snapshots/gradle-1.0-milestone-6-200616+0100-bin.zip a try? Due to a change in our cache format, the first run will need to re-download any dependencies. But I'd expect subsequent dependency resolution to be significantly

Re: [gradle-user] Proper gradle daemon usage

2011-11-04 Thread Hans Dockter
Hi Ed, this is something we are working. You can rest assured that this should be fixed soon. We might ask to try out one of our upcoming snapshots next week that might already will solve your problem. Hans On Fri, Nov 4, 2011 at 11:55 AM, Ed Young e...@summitbid.com wrote: Did the

Re: [gradle-user] Proper gradle daemon usage

2011-11-04 Thread Ed Young
Thanks Hans. Let me know, and I'll take a shot at it. Ed On Fri, Nov 4, 2011 at 7:39 AM, Hans Dockter hans.dock...@gradleware.comwrote: Hi Ed, this is something we are working. You can rest assured that this should be fixed soon. We might ask to try out one of our upcoming snapshots next

[gradle-user] Proper gradle daemon usage

2011-11-03 Thread Ed Young
I need to speed up my development cycle, and I understand the with 1.0-milestone-5 the gradle daemon is greatly improved. How does one use the gradle daemon? I could use an example of how it's used. The docs show command line options but no example. I usually build and run my geb tests like

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Ed Young
This is a very simple geb test. It takes less then 10 seconds to run. The rest of the time it's sitting in: Building :compileTestGroovy Resolve dependencies ':testCompile' The project is modeled after https://github.com/geb/geb-example-gradle The dependencies : dependencies { //groovy

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Ed Young
gradle test -Pt=SimpleNavSpec --daemon takes just as long so there's something else going on. As I said elswhere in this thread, it's sitting in: Building :compileTestGroovy Resolve dependencies ':testCompile' for the majority of the time. How can I speed up this step? On Thu, Nov 3, 2011

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Adam Murdoch
Can you send in your repositories { } section, too? On 04/11/2011, at 6:38 AM, Ed Young wrote: This is a very simple geb test. It takes less then 10 seconds to run. The rest of the time it's sitting in: Building :compileTestGroovy Resolve dependencies ':testCompile' The project is

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Ed Young
certainly: repositories { mavenCentral() mavenRepo urls: [ http://tools-nexus.cable.comcast.com:8080/nexus/content/groups/public/;, https://nexus.codehaus.org/content/repositories/snapshots;, http://repository.codehaus.org;,

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Adam Murdoch
On 04/11/2011, at 9:33 AM, Ed Young wrote: certainly: repositories { mavenCentral() mavenRepo urls: [ http://tools-nexus.cable.comcast.com:8080/nexus/content/groups/public/;, https://nexus.codehaus.org/content/repositories/snapshots;,

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Ed Young
That had the effect of changing it from around 1 minute to more than 2 minutes per dev cycle... I tried a couple variations on what you suggested: repositories { mavenCentral() maven { url http://tools-nexus.cable.comcast.com:8080/nexus/content/groups/public/; } maven { url

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Luke Daley
The simplest way to make this faster would be to avoid the use of snapshots, is that possible? What snapshots are you using? On 03/11/2011, at 11:31 PM, Ed Young wrote: That had the effect of changing it from around 1 minute to more than 2 minutes per dev cycle... I tried a couple

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Ed Young
actually, I'm not using any snapshots anymore, am I. I recently made sure I was using only releases, but I hadn't removed the snapshot repos. Good catch. repositories { mavenCentral() //maven { url http://tools-nexus.cable.comcast.com:8080/nexus/content/groups/public/; } //maven {

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Luke Daley
On 03/11/2011, at 11:50 PM, Ed Young wrote: actually, I'm not using any snapshots anymore, am I. I recently made sure I was using only releases, but I hadn't removed the snapshot repos. Good catch. repositories { mavenCentral() //maven { url

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Ed Young
Wow. 51 seconds for compileTestGroovy. Does that mean it's re-compiling all the groovy test files? This project has many many spec files and page spec files, but I'm not changing any of them and only executing 1 of them. TaskDurationResult Project :52.363s(total)

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Adam Murdoch
On 04/11/2011, at 11:29 AM, Ed Young wrote: Wow. 51 seconds for compileTestGroovy. Does that mean it's re-compiling all the groovy test files? It's almost certainly dependency resolution time. What time does it give on the 'dependency resolution' tab? This project has many many spec

Re: [gradle-user] Proper gradle daemon usage

2011-11-03 Thread Ed Young
DependenciesDuration All dependencies50.814s :testCompile50.053s :testRuntime0.719s :groovyCopy0.041s classpath0.001s :classpath0s On Thu, Nov 3, 2011 at 7:02 PM, Adam Murdoch adam.murd...@gradleware.comwrote: On 04/11/2011, at 11:29 AM, Ed Young wrote: Wow. 51