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. Task Duration Result Project : 52.363s (total) :compileTestGroovy 50.939s UP-TO-DATE :test 1.402s UP-TO-DATE :processTestResources 0.015s UP-TO-DATE :classes 0.002s UP-TO-DATE :compileJava 0.002s UP-TO-DATE :compileGroovy 0.001s UP-TO-DATE :compileTestJava 0.001s UP-TO-DATE :processResources 0.001s UP-TO-DATE :testClasses 0s UP-TO-DATE On Thu, Nov 3, 2011 at 5:53 PM, Luke Daley <[email protected]>wrote: > > 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 " > http://tools-nexus.cable.comcast.com:8080/nexus/content/groups/public/"; } > // maven { url " > https://nexus.codehaus.org/content/repositories/snapshots"; } > // > // mavenRepo url: [ > // "http://repository.codehaus.org";, > // "http://snapshots.repository.codehaus.org"; > // ] > } > > This reduces my dev cycle to slightly less than 1 minute. > > Still not where I need to be. Any other ideas? > > > How long is the test task taking? > > You can run with --profile, which gives you a report > in <build_dir>/reports/profile. > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > -- - Ed
