[GROOVY-7492] Groovy should allow CompileStatic classes to not implement GroovyObject (AKA @POJO)

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Labels: experimental incubating
• Assignee: Paul King
• Reporter: Paul King
• Created: 05/Jul/15 08:58
• Updated: 01/Dec/21 05:59
• Resolved: 11/Sep/20 03:30

Description

Groovy's powerful AST transformation capabilities are extremely useful even in mostly Java projects but the fact that generated classes implement GroovyObject means that Groovy must be on the classpath when using any of the generated artifacts. This proposed new feature allows an opt-out @POJO marker interface which still applies Groovy's AST transforms but then leaves them in a much more Java-like state. The mechanism currently is only enabled when using @CompileStatic since it produces Java-like code. This opens up some of Groovy's powerful transforms to the wider Java community. Groovy can effectively be used as a Lombok-style pre-processor for some Java classes. Note that this is still an experimental feature - it isn't guaranteed at this stage to always produce code which is free from any Groovy jar dependency. As an example, @Immutable for instance might require the Groovy jar. We might also consider producing some trivial size jar if we can't remove all usages of Groovy code.

Issue Links

• links to: GitHub Pull Request #54