http://forums.gradle.org/gradle/topics/mustrunafter_not_a_usable_fix_fot_the_dependson_ordering_bug
There's a point to this. I've found using mustRunAfter to be a little awkward.
We could add some sugar…
taskOrder {
must unitTest, integrationTest, functionalTest
// or
should unitTest, integrationTest, functionalTest
}
same as doing:
integrationTest.mustRunAfter unitTest
functionalTest.mustRunAfter unitTest, integrationTest
Not sure on the names, but you get the idea. I think this would be used to
define all the ordering in one block at the top/end of the build which might
not be a bad thing.
--
Luke Daley
Principal Engineer, Gradleware
http://gradleware.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
