This is just a thought, not a serious interest at this point. Since Groovy targets the JVM and is supposedly a superset of Java, to some extent, it adds additional flexibility to the programmer-centric methodology by allowing easy use of optional types, followed by normal static types in Java, and finally using types in ATS for the most rigor, all while using the JVM. But -- aside from those wanting to target the JVM -- is this really worth it, or does it make better sense to just do co-programming in ATS and a completely dynamically typed language? I hope to get some actual experience with ATS co-programming soon, probably with Perl, so maybe I'll have a better sense then.
I'm aware that currently there is no code generator for Java. I don't know if a code-generator for Groovy would be the right way to go for efficiency reasons, but if it isn't much different, it seems like that might be preferable.
The caveat is, I don't know to what extent Groovy is really a superset of Java, so I don't know if by supporting Groovy code generation you could also claim to have Java support.