On Mon, Oct 29, 2012 at 3:11 AM, Steve Loughran <ste...@hortonworks.com> wrote: > On 27 October 2012 21:51, Wing Yew Poon <wyp...@cloudera.com> wrote: > >> It's good to hear from someone who's been using 1.8. >> I was looking recently at the version of groovy used in itest, and >> surprised that it was such an ancient version (1.6). I'm in favor of >> moving to a more recent stable version like 1.8. I am undecided if we >> should move to 2.x. Since we are not currently using Java 1.7 yet (for >> hadoop etc), I don't see the benefit as far as invokedynamic is >> concerned.
Ok, I've spent a bunch of time (really way more than I should have :-() and it looks that we're may be getting bitten by this issue: http://groovy.329449.n5.nabble.com/groovy-maven-tp4382545p4382976.html Which means that our only option wrt. to bumping the version may only be switching to using this plugin: http://groovy.codehaus.org/Groovy-Eclipse+compiler+plugin+for+Maven In principle, I'm not against changing which plugin we use to compile our Groovy code. The only concern I have is wrt. to our embedded use of Groovy in pom execution steps. Thanks, Roman.
