Hey Marcin, Dzieki for this awesome code ;)
I have some questions about how it works. I know I could probably figure out this from the code/spec but it might be useful for others (plus I didn't see that documented in the docs for the new api methods). Say I configure: foo.mustRunAfter(bar) 1. When I run 'gradle bar' and 'bar' succeeds, does gradle execute 'foo'? 2. When I run 'gradle bar' and 'bar' fails, does gradle execute 'foo'? 3. When I run 'gradle foo bar', what's the order of execution? 4. When bar.dependsOn foo and I run 'gradle bar', what's the order of execution? 5. Is mustRunAfter behavior also respected in an incubating parallel build? Probably not, but just checking :) Cheers! On Thu, Mar 7, 2013 at 11:34 PM, Marcin Erdmann <[email protected]>wrote: > On 07/03/13 09:29, Taytay wrote: > >> As someone who has been following this bug >> <http://issues.gradle.org/**browse/GRADLE-427<http://issues.gradle.org/browse/GRADLE-427>> >> closely for a while, let me >> take a moment to thank you for the work you've done here erdi! >> > I'm happy that you find my contribution useful. It looks like it's a > really old issue and that it affects quite a lot of people. I believe > everyone should be happy that the fix should make it into the codebase in > the foreseeable future. > > > ------------------------------**------------------------------**--------- > To unsubscribe from this list, please visit: > > > http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email> > > > -- 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
