I like this idea -- the use case seems pretty desirable. What about a method named failAtEnd on the Project class? It could take an error message, and an optional exception (for a delayed message with a stack trace).
Sean On Sun, Jan 23, 2011 at 10:10 AM, Hans Dockter <[email protected]> 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? > > Hans > > -- > Hans Dockter > Founder, Gradle > http://www.gradle.org, http://twitter.com/gradleorg > CEO, Gradle Inc. - Gradle Training, Support, Consulting > http://www.gradle.biz >
