thanks for reporting this. I'll have a look on this in the next couple of days and give you feedback.

cheers,
Rene

We are having the exact same issue. I know you are looking into it so I will deactivate for now or roll back the sonar install for a while.

We are also having the same problem. Please let me know when a solution becomes available.

The Sonar plugin will have to undergo bigger changes to work with Sonar 3.4 and higher. Given that Gradle 1.4 is almost out, this will have to wait at least until 1.5.

Thanks for the information, Peter!

For those of you who don ́t want to downgrade your Sonar installation back to <3.4 I have worked out a temporary workaround that hopefully is not too much efford and greatly demonstrates the strenghts of Gradle's Ant integration This is intended to be a relatively simple workaround until Gradle supports Sonar 3.4 again. Unfortunately you need to pass your project settings manually instead of using the Gradle objects, but I guess for most projects it is worth a consideration.

Basic idea is to replace the broken sonarAnalyze task by a custom task that uses the original Sonar Ant task. I am using this solution on a multiproject build and I even did not need to change my CI config because the command line call stays the same.

I hope this helps,
greetings to all Gradlers out there!
Bernd Steinert

To replace the gradle plugin change the line "apply plugin: 'sonar'" to "apply from 'sonar.gradle'" in your build file(s).

sonar.gradle:

apply plugin: 'java'

repositories {
mavenCentral()
}

configurations {
sonar
}

dependencies {
sonar group: 'org.codehaus.sonar-plugins', name: 'sonar-ant-task', version: '2.0'
}

task sonarAnalyze << {

// define the Sonar properties according to Sonar Ant task documentation
ant.properties['sonar.host.url'] = 'http://localhost:9000/sonar'
...

// define multi-project modules
ant.properties['sonar.modules'] = 'mod1,mod2,mod3'

// define module specific properties
ant.properties['mod1.sonar.sources'] = 'other/src/folder'
ant.properties['mod2.sonar.sources'] = 'src,multiple/src/folders'

ant.taskdef(name: 'sonar', classname: 'org.sonar.ant.SonarTask', classpath: configurations.sonar.asPath)

ant.sonar()
}

Thanks for the workaround, I'll give it a try. Peter, do you already have a JIRA to track the necessary changes to support sonar 3.4+?

Oliver

The work is already mostly done. You can try it in the latest nightly.

Is this fixed in 1.5-rc-1? I still have the same problem using gradle-1.5-rc-1 with sonar 3.4.1.

Trying gradle-1.5-rc-1: plugin doesn't seem to work with Sonar 3.5 (same exception).

Just to make sure, when you tried gradle-1.5-rc-1, did you change to using the sonar-runner plugin instead of the sonar plugin? 1.5-rc-1 introduced the sonar-runner plugin, and it is working for me.

http://www.gradle.org/docs/release-candidate/userguide/sonar_runner_plugin.html

No, stupid me - I didn't know I have to use sonar-runner. I'll try it, thanks!