I know, its just that Groovy 1.8 is so cool its hard to resist :) Any time frame on when it will be supported?
Thanks Ronen On Thu, Apr 28, 2011 at 10:33 PM, Peter Niederwieser <[email protected]>wrote: > > Ronen Narkis wrote: > > > > 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 > > > > As I said earlier, implementing plugins with Groovy 1.8 isn't supported at > this point, and one simply cannot tell beforehand if it will work reliably > or not. (The reason is that Groovy doesn't guarantee binary backwards > compatibility between major versions, which admittedly is hard to achieve > for an alternative JVM language. There is at least one known breaking > change > between 1.7 and 1.8, which is related to the use of the 'assert' keyword.) > For plugins that are only used internally, this is obviously a lesser > concern than for plugins shared with the rest of the world. > > -- > 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-tp4342799p4347422.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 > > >
