On 03/11/2011, at 7:06 PM, Ed Young wrote: > 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 this: > gradle test -Pt=SimpleNavSpec > > but that takes 1 min 10 seconds on a very fast laptop! > > CCHL-829706a:func-test-gradle-trunk eyoung2297k$ gradle test -Pt=SimpleNavSpec > The 'urls' property of the RepositoryHandler.mavenRepo() method is deprecated > and will be removed in a future version of Gradle. You should use the 'url' > property to define the core maven repository & the 'artifactUrls' property to > define any additional artifact locations. > :compileJava UP-TO-DATE > :compileGroovy UP-TO-DATE > :processResources UP-TO-DATE > :classes UP-TO-DATE > :compileTestJava UP-TO-DATE > :compileTestGroovy UP-TO-DATE > :processTestResources UP-TO-DATE > :testClasses UP-TO-DATE > :test UP-TO-DATE > > BUILD SUCCESSFUL > > Total time: 1 mins 9.609 secs > > How can I speed this up using the gradle daemon?
Two ways: gradle test -Pt=SimpleNavSpec --daemon Or set the JVM sys prop org.gradle.daemon to 'true' e.g. export GRADLE_OPTS="-Dorg.gradle.daemon=true" -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
