[ANN] Groovy-Eclipse 2.1.2 Released

[Andrew Eisenberg]

Hi all,

Today, we have officially released Groovy-Eclipse 2.1.2.  This release
includes many improvements including inline renaming support,
mark/find occurrences as you type, and type inferencing improvements.
You can find all the details at the New and Noteworthy page
(http://docs.codehaus.org/display/GROOVY/Groovy-Eclipse+2.1.1RC1+New+and+Noteworthy)

The update site for installation on Eclipse 3.6 is here:

http://dist.springsource.org/milestone/GRECLIPSE/e3.6/

We are also now releasing a Groovy-Eclipse for Eclipse 3.7 (Indigo).
The update site is here:

http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/

As always, please raise bug reports and enhancement requests at
http://jira.codehaus.org/browse/GRECLIPSE

General questions can be sent to the
[hidden email] mailing list.  We are looking
forward to your feedback.

Andrew Eisenberg

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Andrew Eisenberg]

Apologies, everyone.  I sent the wrong link for the N&N.  Here is the real one:

http://docs.codehaus.org/display/GROOVY/Groovy-Eclipse+2.1.2+New+and+Noteworthy



On Fri, Mar 18, 2011 at 9:31 AM, Andrew Eisenberg <[hidden email]> wrote:

> Hi all,
>
> Today, we have officially released Groovy-Eclipse 2.1.2.  This release
> includes many improvements including inline renaming support,
> mark/find occurrences as you type, and type inferencing improvements.
> You can find all the details at the New and Noteworthy page
> (http://docs.codehaus.org/display/GROOVY/Groovy-Eclipse+2.1.1RC1+New+and+Noteworthy)
>
> The update site for installation on Eclipse 3.6 is here:
>
> http://dist.springsource.org/milestone/GRECLIPSE/e3.6/
>
> We are also now releasing a Groovy-Eclipse for Eclipse 3.7 (Indigo).
> The update site is here:
>
> http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/
>
> As always, please raise bug reports and enhancement requests at
> http://jira.codehaus.org/browse/GRECLIPSE
>
> General questions can be sent to the
> [hidden email] mailing list.  We are looking
> forward to your feedback.
>
> Andrew Eisenberg
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[virtualeyes]

Andrew, thanks for the great work.

What is the @ETA for 1.8 support? Couple of days, weeks or months?

Annotation closures are generating syntax errors in STS 2.6 (which uses 1.7.8 runtime), while in groovy console (which uses classpath groovy runtime 1.8 RC-3), works without issue.

Noah

[Andrew Eisenberg]

I would say in a week or so for 1.8 support.  The reason why
annotation closures is causing errors is, as you say, because
Groovy-Eclipse is using the 1.7 compiler.

On Fri, Mar 18, 2011 at 1:28 PM, virtualeyes <[hidden email]> wrote:

> Andrew, thanks for the great work.
>
> What is the @ETA for 1.8 support? Couple of days, weeks or months?
>
> Annotation closures are generating syntax errors in STS 2.6 (which uses
> 1.7.8 runtime), while in groovy console (which uses classpath groovy runtime
> 1.8 RC-3), works without issue.
>
> Noah
>
> --
> View this message in context: http://groovy.329449.n5.nabble.com/ANN-Groovy-Eclipse-2-1-2-Released-tp3970883p3983148.html
> Sent from the groovy - user mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[virtualeyes]

Andrew,

OK, not a deal breaker, just annoying that STS flags apparent 1.8 related syntax errors, while running the code in Tomcat or Groovy Console (through 1.8 RC3) shows that the code is error-free.  The price for early adoption I guess...

Looking forward to 1.8 support, the Groovy train is on the move ;--)

Noah

[Andre Steingress]

Andrew Eisenberg wrote

The reason why annotation closures is causing errors is, as you say, because
Groovy-Eclipse is using the 1.7 compiler.

This is not entirely true. For example, GContracts replaces annotation closure parameters (which are syntactically allowed even in 1.7 as far as I know) with generated Closure classes - since Class parameters are allowed as annotation parameters this will let the annotation compile. (In fact this is the way how annotations closures are handled in Groovy 1.8 btw)

The problem is that GContracts is a global AST transformation which is not taken into account by the Eclipse Groovy compiler, therefore the editor shows the annotation closure as error but the compilation itself will run through.

Cheers, Andre

[Andy Clement]

> The problem is that GContracts is a global AST transformation which is not
> taken into account by the Eclipse Groovy compiler, therefore the editor
> shows the annotation closure as error but the compilation itself will run
> through.

Yep, that is jira issue: https://issuetracker.springsource.com/browse/STS-1154
On some kinds of compile we don't run all transforms right now,
deliberately, as some of them interfere with other things that are
going on.  The editor error is shown by the reconcile compile which
does not run that transform.

Andy

On 18 March 2011 14:53, Andre Steingress <[hidden email]> wrote:

>
> Andrew Eisenberg wrote:
>>
>> The reason why annotation closures is causing errors is, as you say,
>> because
>> Groovy-Eclipse is using the 1.7 compiler.
>>
>
> This is not entirely true. For example, GContracts replaces annotation
> closure parameters (which are syntactically allowed even in 1.7 as far as I
> know) with generated Closure classes - since Class parameters are allowed as
> annotation parameters this will let the annotation compile. (In fact this is
> the way how annotations closures are handled in Groovy 1.8 btw)
>
> The problem is that GContracts is a global AST transformation which is not
> taken into account by the Eclipse Groovy compiler, therefore the editor
> shows the annotation closure as error but the compilation itself will run
> through.
>
> Cheers, Andre
>
> --
> View this message in context: http://groovy.329449.n5.nabble.com/ANN-Groovy-Eclipse-2-1-2-Released-tp3970883p3988362.html
> Sent from the groovy - user mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Andre Steingress]

In case of GContracts it is not a big deal, cause one can argue that its usage is supported in STS/Eclipse starting with the annotation closure feature in 1.8.

It has just been confusing for Eclipse users (jira issue) to see error markers in the source-code with actually no compile-time errors.

Cheers, Andre