On 17/02/2012, at 10:21 AM, Russel Winder wrote: > On Fri, 2012-02-17 at 10:00 +0000, Luke Daley wrote: > [...] >> >> Do you mean the task “check”? If so, it's a lifecycle task that is added by >> java-base plugin. It has no actions itself, but is a meeting point for >> verification tasks. >> >> So the idea is that ./gradlew check executes all of the different kinds of >> checks in your project. The code quality plugins make their tasks >> dependencies of this task. >> >> See: >> https://github.com/gradle/gradle/blob/master/subprojects/code-quality/src/main/groovy/org/gradle/api/plugins/quality/internal/AbstractCodeQualityPlugin.groovy#L121 > > OK, the problem is then that if one of the checks raises errors then > Gradle terminates which means the later ones do not run. > > My comment must therefore be amended to: Gradle should run all the > tasks associated with a lifecycle task not just those until the first > check fail discovery. > > Does this make sense?
Right. That's currently impossible, but seems like a reasonable feature. For the time being you can get close by running with --continue, but it's not quite the same thing. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
