I know you are in the process of fixing sonarRunner with Gradle 2.2 so this may be too early to report. I'm seeing the following when I do "gradlew sonarRunner" using gradle nightly 2.2-20140910134745+0000

at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:65)
... 1 more
Caused by: java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.7.0_67\bin\java.exe" (in directory "J:\git\gradledemo\access"): CreateProcess error=206, The filename or extension is too long
at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start(DefaultProcessLauncher.java:25)
... 4 more
Caused by: java.io.IOException: CreateProcess error=206, The filename or extension is too long

Full stacktrace here
[1]https://gist.github.com/bradthurber/c...

I suspect it may not like like the space in "C:\Program Files"? I could always install java somewhere else, but I thought this would be worth fighting through since it is the default location Oracle specifies on setup.

This is my first attempt at using Sonar in quite some time so it is quite possible there is a configuration issue on my part as well. The relevant part of my build.gradle:

apply plugin: 'sonar-runner'
sonarRunner {
sonarProperties {
property "sonar.host.url", "http://localhost:9000/"
property "sonar.jdbc.url", "jdbc:h2:tcp://localhost:9092/sonar"
property "sonar.jdbc.driverClassName", "org.h2.Driver"
property "sonar.jdbc.username", "sonar"
property "sonar.jdbc.password", "sonar"
}
}

----------------------------------------------------------------------------------------
[1] https://gist.github.com/bradthurber/c3fe4ba672d9c9ef7064