Hmm, I could swear that task execution was ordered in 0.9.2; I'm going mad perhaps ;-)
Rene, I've fixed the latest build by adding clean as a dependency on allTests. Gradleware folks, I understand Gradle will inspect the DAG and optimize task execution however I would very much like GRadle to honor my request and execute some tasks as I specified. >________________________________ > From: Rene Groeschke <[email protected]> >To: [email protected] >Sent: Monday, December 12, 2011 11:11 AM >Subject: Re: [gradle-user] Task execution order broken? > >Hi Andres, >The dependsOn declarations in gradle are not ordered. The default is >running them in the alphabetical order. That's the reason why 'allTests' >is executed before 'clean'. A quickfix for that can be to make allTests >depend on clean. Maybe we can move this discussion to the griffon >mailinglist and you explain what you try to achieve and we find a more >gradle like solution together? > >regards, >René > > >> Hi All, >> >> We've been experiencing trouble in the Griffon build, particularly with >> task execution order. >> Our main build file defines the following tasks >> >> task allTests(dependsOn: [project(':griffon-rt').test, >> project(':griffon-cli').test]) { >> description = "Runs all tests." >> } >> >> task fullDist(dependsOn: [zipBinary, zipSource, tarBinary, tarSource, >> izpack, deb]) { >> description = "Assembles all packages." >> } >> >> task bambooStage1(dependsOn: [clean, allTests]) { >> description = "Makes a full test run and assembles all packages." >> } >> >> calling `gradle bambooStage` >> >> yields the following output >> >> :buildSrc:compileJava UP-TO-DATE >> :buildSrc:compileGroovy >> :buildSrc:processResources UP-TO-DATE >> :buildSrc:classes >> :buildSrc:jar >> :buildSrc:assemble >> :buildSrc:compileTestJava UP-TO-DATE >> :buildSrc:compileTestGroovy UP-TO-DATE >> :buildSrc:processTestResources UP-TO-DATE >> :buildSrc:testClasses UP-TO-DATE >> :buildSrc:test >> :buildSrc:check >> :buildSrc:build >> :griffon-rt:compileJava UP-TO-DATE >> :griffon-rt:compileGroovy >> :griffon-rt:processResources >> :griffon-rt:classes >> :griffon-rt:jar >> :griffon-cli:compileJava UP-TO-DATE >> :griffon-cli:compileGroovy >> :griffon-cli:processResources >> :griffon-cli:classes >> :griffon-cli:compileTestJava UP-TO-DATE >> :griffon-cli:compileTestGroovy >> :griffon-cli:processTestResources >> :griffon-cli:testClasses >> :griffon-cli:test >> :griffon-rt:compileTestJava UP-TO-DATE >> :griffon-rt:compileTestGroovy >> :griffon-rt:processTestResources UP-TO-DATE >> :griffon-rt:testClasses >> :griffon-rt:test >> :allTests >> :griffon-cli:clean >> :griffon-guide:clean UP-TO-DATE >> :griffon-resources:clean UP-TO-DATE >> :griffon-rt:clean >> :griffon-scripts:clean UP-TO-DATE >> :griffon-wrapper:clean UP-TO-DATE >> :clean UP-TO-DATE >> :bambooStage1 >> >> >> >> As you can appreciate clean is called way after allTests has been >> executed. We're running with 1.0-milestone-6. It's worth mentioning that >> the correct order was executed with 0.9.2. >> Any ideas of what may be happening here? >> >> TIA >> Andres >> >> >> ------------------------------------------------------------ >> Gradle 1.0-milestone-6 >> ------------------------------------------------------------ >> Gradle build time: Thursday, November 17, 2011 5:54:12 AM UTC >> Groovy: 1.8.4 >> Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010 >> Ivy: 2.2.0 >> JVM: 1.6.0_29 (Apple Inc. 20.4-b02-402) >> OS: Mac OS X 10.6.8 x86_64 >> >> >> >> ------------------------------------------- >> http://jroller.com/aalmiray >> http://www.linkedin.com/in/aalmiray >> -- >> What goes up, must come down. Ask any system administrator. >> There are 10 types of people in the world: Those who understand binary, >> and those who don't. >> To understand recursion, we must first understand recursion. > > > >--------------------------------------------------------------------- >To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > >
