The 'sonar' task doesn't depend on any other tasks, which makes it more flexible to use. Typically, you should have your code compiled and test reports generated before running it. If you want it to 'just work', run 'gradle build sonar'.
As the core Gradle distribution doesn't come with a Cobertura plugin, the Sonar plugin doesn't (and cannot) tell Sonar about the location of Cobertura reports. You'll have to do this yourself by way of adding a 'projectProperty'. The Sonar plugin documentation contains a link to the Sonar page that documents available configuration properties. Also see the DSL reference for the 'sonar' task: http://www.gradle.org/current/docs/dsl/org.gradle.api.plugins.sonar.Sonar.html -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Blog: http://pniederw.wordpress.com Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/questions-about-sonar-plugin-tp4416266p4435439.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
