Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
1.0
-
None
-
All
Description
There are some use cases for which it would be desirable to be able to use Groovy as a 'better Java'. That is, that Groovy should compile down to pure Java .class files, with absolutely no runtime dependencies, even if that means we lose some of Groovy's beyond-Java abilities.
The current runtime dependency on GroovyObject means we have to ship an additional 2MB worth of JARs with our app, which is unacceptable for rich client apps.
An example of such a use case would be:
- Using GroovyBeans as a shorthand for defining all the getters/setters in a JPA entity: http://www.curious-creature.org/2007/03/25/persistence-made-easy-with-groovy-and-jpa