If this is about using Class.forName to load JDBC drivers from a dynamically constructed classpath, then this issue came up with Groovy Grapes too. The solution in the end (from the user's perspective) was the @GrabConfig(systemClassLoader=true) setting.
On Wed, 2011-01-26 at 08:53 -0800, Peter Niederwieser wrote: > You are running into a typical class loading problem that also occurs with > app servers. The class loader for Groovy/Gradle sits atop the class loader > for the build script. Hence the groovy.sql.Sql class cannot see the > org.postgresql.Driver class. Currently I don't know of a better way than to > put the driver Jar into Gradle's lib directory. Please raise an issue for > this. > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradle Inc. > http://www.gradle.biz > Founder, Spock Framework > http://spockframework.org > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
