On 23/01/2011, at 9:10 PM, Hans Dockter wrote: > A task might produce information that is sufficient to let the build fail > (e.g. a failing test). But the output of the task is still complete (in > contrast to a failing compile) so the build could continue with gathering > more information (e.g. failing tests in other subprojects). But the build > should fail at the end. > > What about giving every task a property like: failAtEnd > > At the end (or in the case of an immediate fail) we would list all delayed > error messages. > > Thoughts?
I think this would be very useful. I wonder, though, if this is a function of the type of build being performed, rather than of a task, ie perhaps this should be a global setting on the Gradle instance. Or, perhaps, Gradle should always work this way. That is, Gradle always attempts to perform as much of the requested work as possible, even in the presence of failures. -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
