> > 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. > Roman, I took a look at groovy-eclipse-compiler. From what I read, the drawback of groovy-eclipse-compiler is that groovy scripts cannot be executed in your poms. So what is the plan for the embedded groovy in the poms (I see that there is embedded groovy in
bigtop-tests/test-artifacts/package/pom.xml bigtop-tests/test-execution/common/pom.xml )? Do we use gmaven-plugin for that alongside groovy-eclipse-compiler for building? And the gmaven-plugin uses an older groovy? - Wing Yew
