Mailing-List: contact notifications-help@groovy.incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.incubator.apache.org
Date: Sun, 5 Jul 2015 09:24:04 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: notifications@groovy.incubator.apache.org
Message-ID: <JIRA.12842724.1436086718000.100290.1436088244571@Atlassian.JIRA>
In-Reply-To: <JIRA.12842724.1436086718000@Atlassian.JIRA>
References: <JIRA.12842724.1436086718000@Atlassian.JIRA>
 <JIRA.12842724.1436086718793@arcas>
Subject: [jira] [Commented] (GROOVY-7492) Groovy should allow CompileStatic
 classes to not implement GroovyObject
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/GROOVY-7492?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D146=
14192#comment-14614192 ]=20

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=
=E2=80=A6

    =E2=80=A6nt 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
   =20
----
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 ev=
en in mostly Java projects but the fact that generated classes implement Gr=
oovyObject 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 leav=
es them in a much more Java-like state. The mechanism currently is only ena=
bled when using @CompileStatic since it produces Java-like code. This opens=
 up some of Groovy's powerful transforms to the wider Java community. Groov=
y can effectively be used as a Lombok-style pre-processor for some Java cla=
sses. 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 dep=
endency.


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