Matthew, GRADLE-1467 was caused by a Groovy bug/limitation that only manifests itself when compiling Gradle with JDK 5 (this is what we currently do for the releases) and running it with JDK 6. To find such issues sooner in the future, we'll have to find a way to model this setup with a CI build.
As of the Gradle 1.0 milestone 3 release, the Sonar plugin works fine for me (tested with Sonar server 2.6). We integrate with Sonar via sonar-batch-boostrapper-2.6, which automatically downloads the required Sonar client libraries from the Sonar server and loads them via a completely isolated class loader. As long as the Gradle Sonar plugin is part of the Gradle distribution, you'll be able to use those versions of Sonar with Gradle that the bootstrapper we are shipping is compatible with. sonar-batch-boostrapper-2.6 is said to be compatible with Sonar 2.6 and higher. Manually replacing some of the libraries in the Gradle distribution is unlikely to help. At first glance, the NoSuchMethodError looks like a Sonar issue to me, but this is just an educated guess. Do you have a GitHub project that allows me to reproduce the error? -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradleware http://www.gradleware.com Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Sonar-Plugin-throws-java-lang-NoSuchMethodError-on-Milestone-3-tp4344291p4345147.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
