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? -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
