You can use the --continue command-line option. On 28/04/2012, at 12:20 AM, AlanKrueger wrote:
> > Adam Murdoch-2 wrote >> >> On 14/05/10 5:37 AM, Shay Banon wrote: >>> Hi, >>> >>> Can this be done now in 0.9? I mean, in a multi project build, have >>> the >>> whole build fail if one of the sub projects failed, but only at the end >>> *after* it ran all the sub projects tests. Also, I think this should be >>> the >>> default behavior. >>> >> >> This can't be done in 0.9. >> >> I agree it should be the default behaviour, and possibly the only >> behaviour. Gradle should try to complete as much of the requested work >> as it can, subject to task dependencies, rather than just stopping on >> the first failure. This should be true, not just for failed tests, but >> for everything that Gradle does: checkstyle, compilation, downloads, >> javadoc, whatever. >> >> -- >> Adam Murdoch >> Gradle Developer >> http://www.gradle.org >> > > Sorry to resurrect a really old thread, but did this ever get implemented? > > It's necessary if a test starts failing in a dependency, as otherwise new > errors (even compile errors) on dependent projects will be masked until the > broken test is fixed. > > Thanks, > Alan Krueger > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Testing-in-multi-project-builds-tp1435498p5670423.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
