Yes, the problem was the wrong driver class name. Changing com.postgresql.Driver to org.postgresql.Driver solved that problem.
I would recommend trying to differentiate between Sonar configuration errors and internal errors. I had a couple of other configuration errors (couldn't open connection to DB because it wasn't taking remote connections, invalid credentials) and they all started with "FAILURE: Build aborted because of an internal error". - David On Fri, Apr 29, 2011 at 12:44 AM, Peter Niederwieser <[email protected]>wrote: > > David Resnick wrote: > > > > 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. > > > > Yes, I think that due to your server configuration, only postgreSQL driver > will be downloaded. > > -- > 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-tp4345660p4353021.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 > > >
