groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GROOVY-7492) Groovy should allow CompileStatic classes to not implement GroovyObject
Date Sun, 05 Jul 2015 09:24:04 GMT

    [ https://issues.apache.org/jira/browse/GROOVY-7492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614192#comment-14614192
] 

ASF GitHub Bot commented on GROOVY-7492:
----------------------------------------

GitHub user paulk-asert opened a pull request:

    https://github.com/apache/incubator-groovy/pull/54

    GROOVY-7492: Groovy should allow CompileStatic classes to not impleme…

    …nt GroovyObject

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/paulk-asert/incubator-groovy groovy7492

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-groovy/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #54
    
----
commit e7dc41066fb6db3ef0e164040c0665ae50414617
Author: paulk <paulk@asert.com.au>
Date:   2015-07-05T09:04:17Z

    GROOVY-7492: Groovy should allow CompileStatic classes to not implement GroovyObject

----


> Groovy should allow CompileStatic classes to not implement GroovyObject
> -----------------------------------------------------------------------
>
>                 Key: GROOVY-7492
>                 URL: https://issues.apache.org/jira/browse/GROOVY-7492
>             Project: Groovy
>          Issue Type: New Feature
>            Reporter: Paul King
>            Assignee: Paul King
>              Labels: experimental
>             Fix For: 2.5.0-beta-1
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message