Iv tried to use groovy 1.8 in a plugin that I'm writing, seems like the groovy version that my plugin depends upon isn't provided on runtime by default:
Cause: java.lang.NoClassDefFoundError: groovy.json.JsonSlurper Adding: classpath 'org.codehaus.groovy:groovy:1.8.0' to the buildfile script worked but I'm not sure its the way to go Ronen On Thu, Apr 28, 2011 at 8:45 PM, Peter Niederwieser <[email protected]>wrote: > > Jesper Skov wrote: > > > > I have some Gradle plugins compiled with Groovy 1.8, but they fail to > load > > in 1.0-milestone-3 since it uses Groovy 1.7.10 (according to 'groovy > -v'). > > > > Can you post the stack trace(s)? I'm curious to learn what the problems > are. > > > Jesper Skov wrote: > > > > Is there some way to coax Gradle into using another Groovy? > > > > There isn't, at least not officially. You could try to replace the Groovy > Jar in the Gradle distribution, but since Gradle's own Groovy classes get > compiled with that Groovy version (1.7.10 at this time), you will probably > run into similar problems. > > In general, Groovy doesn't guarantee binary backwards compatibility between > major versions. This means that you might only be able to use Gradle > plugins > compiled against the same major Groovy version as the one Gradle uses. > That's one of the reasons why some Groovy libraries (for example Gant and > Spock) ship separate Jars for every major Groovy version. > > -- > 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/ANN-Gradle-1-0-milestone-3-released-tp4342799p4347147.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 > > >
