I can't check this until next week, but it makes sense that this is the problem. The sample sonar.properties file has org.postgresql.Driver.
Thanks a lot for looking into this for me! Just as a test I did also try to run the plugin without configuring the driverClassName and got a ClassNotFoundException for org.apache.derby.jdbc.ClientDriver (the stack trace is in the jira I opened). This is probably because the server is configured to use postgresql though. - David On Thu, Apr 28, 2011 at 11:00 PM, Peter Niederwieser <[email protected]>wrote: > After talking back to the Sonar folks, it turns out that Sonar > automatically > provides drivers for MySQL 5.1.x, PostgreSQL and MS SqlServer 2005. Only > for > Oracle you have to provide the driver on your own, but to the Sonar web > application (!) rather than to Gradle. (The Gradle Sonar plugin will > download the driver automatically from the server.) You still have to > configure the driver class name in the Gradle Sonar task though, just as > you > did. > > Coming back to your problem, I think you may have mixed up the PostgreSQL > driver class name. According to Google, the name is "org.postgresql.Driver" > rather than "com.postgresql.Driver". Let us know if this solves your > problem. > > -- > 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/Adding-postgresql-driver-to-sonar-task-tp4345660p4347628.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 > > >
