Hi there, I had a look at the gpars build file and indeed it seems that the docs anttask has a dependency to commons-logging. adding
---------- docs group: 'commons-logging', name: 'commons-logging', version: '1.1' ---------- to the dependencies fixed my local gpars build. regards, René Am 15.11.10 21:19, schrieb Adam Murdoch: > > On 16/11/2010, at 6:48 AM, Russel Winder wrote: > >> Hans, Adam, >> >> I just tried Gradle 0.9-rc-3 with the GPars build and it fails as rc-2 >> did with: >> >> FAILURE: Build failed with an exception. >> >> * Where: >> Build file '/home/users/russel/Repositories/Git/Git/GPars/build.gradle' line: 186 >> >> * What went wrong: >> Execution failed for task ':docs'. >> Cause: java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory > > Is this using an Ant task? > > Prior to 0.9-rc-2, the Ant classes were loaded by the same ClassLoader that loads the rest of the Gradle implementation. In 0.9-rc-2, the Ant ClassLoader was split out so that it contains only Ant classes. This means that Ant tasks should see a ClassLoader hierarchy very similar to what they see when running in Ant itself. > > However, some Gradle builds will break if the taskdefs that they use accidentally left out a dependency which happened to be previously visible from the Gradle implementation ClassLoader. For example, commons logging. > > So, you might check the classpath that you use to taskdef the Ant task and make sure it includes all the actual dependencies of the task. > > > -- > Adam Murdoch > Gradle Developer > http://www.gradle.org > CTO, Gradle Inc. - Gradle Training, Support, Consulting > http://www.gradle.biz > > -- ------------------------------------ Rene Groeschke [email protected] http://www.breskeby.com http://twitter.com/breskeby ------------------------------------
