vorg (aka Gavin), can you proof your 2011 statement about the duplication? Neither was there a copy&paste, nor is there a big overlap in concepts that goes beyond what these would have in common with javac for example.
And another thing... Grails has nothing to do with Groovy on Android. And thanks to some fixes I did with Cedric you don't need to statically compile the groovy code either.
mid 2009: Alex Tkachman began work on Groovy++, a statically typed plugin to Groovy's AST, which the Groovy project management said they didn't want [1]
mid 2010: Groovy 1.8 beta 2 broke Groovy++ which had to switch back to Groovy 1.7
late 2011: SpringSource employed Cedric Champeau to duplicate most of the Groovy++ code and renamed Groovy 1.9 to 2.0.0-beta-1, dropping other features like the Java 8 lambda retrofit and meta-object protocol cleanup
mid 2012: Official standalone release of Groovy 2.0 was really just another beta to encourage more people to test it
Dec 2012: Grails 2.2 released with groovy 2.0.5 bundled, after being tested by programmers who thought Groovy had any real intended use as a standalone language outside of Grails. Grails 2.2 doesn't, however, actually use the static compilation features of Groovy, just wanted to know it would run with Groovy 2.0 bundled without breaking.
mid 2013: Groovy 2.1 was the first release with most @CompileStatic bugs fixed
May 2014: Grails 2.4 released, the first to actually use any of the @CompileStatic features of Groovy, but with this strong caution in the doco: "Care must be taken when deciding to statically compile code." [2]
[1] http://groovy.329449.n5.nabble.com/On-static-compilation-of-...
[2] http://grails.org/doc/2.4.0.M1/guide/introduction.html#whats...