I agree that "faster feedback" use cases are better solved with "shouldRunAfter", especially if you consider parallel execution.
Cheers! On Thu, Apr 11, 2013 at 5:02 PM, Marcin Erdmann <[email protected]>wrote: > On 11/04/13 08:55, Adam Murdoch wrote: > > > On 11/04/2013, at 4:01 PM, Hans Dockter <[email protected]> > wrote: > > 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). > > > Just to let you know, I'm happy to work on that as soon as you find it > reasonable. > -- Szczepan Faber Principal engineer@gradleware; Lead@mockito Join me at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com
