On 11/04/2013, at 4:01 PM, Hans Dockter <hans.dock...@gradleware.com> wrote:
> Just read in the userguide the new section on Task Ordering: > http://www.gradle.org/docs/nightly/userguide/more_about_tasks.html#sec:ordering_tasks > > We describe as a use case for mustRunAfter: > > Specify that unit tests should always run before integration tests for faster > feedback, but still allow integration tests to be run without unit tests. > > This is a use case for a future shouldRunAfter relationship. Using > mustRunAfter here can lead to trouble as it can easily introduce a cyclic > violation for no good reason. We should point this out in the user's guide > that mustRunAfter is a (often very good) work around for this use case but > not the final solution. > > What is the plan for introducing shouldRunAfter? No plan yet. It's on the wish list. I think I'd like to let what we have soak for a while so that people can find out what's wrong with it before we continue on with more. Unless use cases which need the new stuff come along sooner, that is (the deployment stuff, for example). > Although I agree that the mustRunAfter is more important than shouldRunAfter. > But I don't think that shouldRunAfter isan exotic use case. There are many > feedback accelleration scenarios where you want to have that. Obviously the > Ant import would be another grateful consumer. Absolutely. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com
