[groovy-user] [ANN] Groovy-Eclipse 2.1 compiler support and Kepler builds now available

[Andrew Eisenberg]

Today is your lucky day! Two announcements for the price of one.

Groovy-Eclipse now supports the Groovy 2.1 compiler as an optional
add-on (Eclipse 3.8, 4.2, and 4.3 builds only). You can install from
the snapshot update site. The new @DelegatesTo annotation is
supported as well.

Also, we now have Eclipse 4.3 (Kepler) support for Groovy-Eclipse.
These are snapshot builds only and installing Groovy-Eclipse 4.3 will
downgrade your JDT to use the 3.8 JDT (i.e, the JDT for the Juno
release). This is less scary than it sounds since there are few
changes between the 3.8 and 3.9 JDT versions.

Eclipse 4.2 and 4.3 update sites (with Groovy 2.1 support):
http://dist.springsource.org/snapshot/GRECLIPSE/e4.2/
http://dist.springsource.org/snapshot/GRECLIPSE/e4.2/

In order to keep our build process simpler and shorter, we will no
longer be shipping regular snapshots (or new releases of)
Groovy-Eclipse for Eclipse 3.7 (Indigo). If there are requests for
specific builds then we can create them.

See here for more information on how to install:
http://docs.codehaus.org/display/GROOVY/Eclipse+Plugin Feedback is
welcome.

thanks all,
Andrew

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

http://xircles.codehaus.org/manage_email

[Cédric Champeau]

Congratulations for the release !

Le 07/02/2013 21:04, Andrew Eisenberg a �crit :

--
C�dric Champeau
SpringSource - A Division Of VMware
http://www.springsource.com/
http://twitter.com/CedricChampeau

[Guillaume Laforge]

+1, excellent news, congrats :-)

On Thu, Feb 7, 2013 at 9:10 PM, Cédric Champeau <cedric....@gmail.com> wrote:

Congratulations for the release !

--
Cédric Champeau

SpringSource - A Division Of VMware
http://www.springsource.com/
http://twitter.com/CedricChampeau

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

   http://xircles.codehaus.org/manage_email

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

[OC]

Hello there,

On Feb 7, 2013, at 9:04 PM, Andrew Eisenberg <and...@eisenberg.as> wrote:
> Groovy-Eclipse now supports the Groovy 2.1 compiler

Well great, but I've bumped into a weird problem.

When I build the project, I'm getting the error

Description Resource Path Location Type
Groovy compiler level expected by the project does not match workspace compiler level.
Project compiler level is: 2.0
Workspace compiler level is 2.1
Go to Project properties -> Groovy compiler to set the Groovy compiler level for this project CEBOIS CEBOIS Groovy compiler mismatch problem

In the project properties though, there is no 2.1 -- I can select only from 1.7, 1.8 and 2.0. Which _is_ rather weird, for I don't even have 1.7 and 1.8; on the other hand, I do have 2.1:

Groovy Compiler 2.0 Feature 2.8.0.xx-20130205-1700-e42 org.codehaus.groovy20.feature.feature.group Codehaus.org
Groovy Compiler 2.1 Feature 2.8.0.xx-20130205-1700-e42 org.codehaus.groovy21.feature.feature.group Codehaus.org

Note: Eclipse 3.8 -- I had to downgrade lately from 4.2, since WOLips crashed in there.

Eclipse SDK 3.8.2.M20130131-0800 org.eclipse.sdk.ide null

Any help?

Thanks a lot,
OC

[OC]

P.S.

On Feb 8, 2013, at 8:50 AM, OC <o...@ocs.cz> wrote:

In the project properties though, there is no 2.1 -- I can select only from 1.7, 1.8 and 2.0. Which _is_ rather weird, for I don't even have 1.7 and 1.8; on the other hand, I do have 2.1:

I do have 1.8, I've forgot. Definitely thogugh I haven't 1.7.

Possibly this mess might be related to the pretty strange picture I am getting in Installed Software, as I wrote a week ago in "Re: [groovy-user] manage imports for an Eclipse/Groovy project" of Fri, 1 Feb 2013 19:55:16 -- now with 2.1 installed it looks like this, which seems fishy; is it normal to look this way? And if not, might please some Eclipse Guru advice how to fix the problem?

Thanks a very big lot,

OC

[Andrew Eisenberg]

This picture makes sense.  Features can be installed as top level features, or as dependent features.  Looks like Groovy 2.0 and 1.8 are installed as dependent features (which is how things are set up now---the Groovy-Eclipse feature depends on the Groovy 2.0 and 1.8 features).  The groovy 2.0 feature is *also* installed as a top level feature.  Groovy 2.1 is installed top-level as well.

As for not being able to switch to version 2.1.  Looks like it is a bug in the UI. The 2.1 version is just not showing up.  You have 3 possibilities to work around this:

1. open your Project/.settings/org.eclipse.jdt.groovy.core.prefs file and change the groovy.compiler.level to 21
2. select project, right-click -> Groovy -> Fix compiler mismatch problems.  Choose all appropriate projects.  Click 'Yes'.
3. Preferences -> Groovy -> Compiler de-select "Enable checking for compiler mismatches..."

Easy enough fix and I'll get a new build out soon.  Thanks for letting me know.

[OC]

Andrew,

thanks a lot!

On Feb 8, 2013, at 6:35 PM, Andrew Eisenberg <and...@eisenberg.as> wrote:

> This picture makes sense. Features can be installed as top level features, or as dependent features. Looks like Groovy 2.0 and 1.8 are installed as dependent features (which is how things are set up now---the Groovy-Eclipse feature depends on the Groovy 2.0 and 1.8 features). The groovy 2.0 feature is *also* installed as a top level feature. Groovy 2.1 is installed top-level as well.

Should I uninstall then the top-level 2.0? Or does that not matter?

> As for not being able to switch to version 2.1. Looks like it is a bug in the UI. The 2.1 version is just not showing up. You have 3 possibilities to work around this:
> 1. open your Project/.settings/org.eclipse.jdt.groovy.core.prefs file and change the groovy.compiler.level to 21

Yup, that I did :)

> 2. select project, right-click -> Groovy -> Fix compiler mismatch problems. Choose all appropriate projects. Click 'Yes'.
> 3. Preferences -> Groovy -> Compiler de-select "Enable checking for compiler mismatches..."

Didn't know of these two, thanks!

> Easy enough fix and I'll get a new build out soon. Thanks for letting me know.

Oh, never mind -- I thank you for the quick responses and great support!

Thanks and all the best,

[Andrew Eisenberg]

> Should I uninstall then the top-level 2.0? Or does that not matter?

No. Doesn't matter.