groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harry Chan (JIRA)" <>
Subject [jira] [Commented] (GROOVY-7492) Groovy should allow CompileStatic classes to not implement GroovyObject
Date Sun, 11 Feb 2018 08:10:00 GMT


Harry Chan commented on GROOVY-7492:

This is another case about this issue. The Weld (CDI reference implementation) Decorator does
NOT work with Groovy because every Groovy class and interface implemented GroovyObject.

Please check: []

> Groovy should allow CompileStatic classes to not implement GroovyObject
> -----------------------------------------------------------------------
>                 Key: GROOVY-7492
>                 URL:
>             Project: Groovy
>          Issue Type: New Feature
>            Reporter: Paul King
>            Priority: Major
>              Labels: experimental
> 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.

This message was sent by Atlassian JIRA

View raw message