What if you want to develop Grails 3 projects with Eclipse Mars (4.5) as easy as you did with Groovy/Grails Tool Suite or previous Eclipse versions? Written and tested with Eclipse Mars.1 Release (4.5.1, build 20150924-1200) and Grails 3.1.0 M1.
Continue reading “Eclipse Mars: Grails 3.1 with Gradle, Groovy and GSP Support”
Grails 3 has been released with a ton of new features.
If you’re used to adding a new Grails distribution in Eclipse or Groovy/Grails Tool Suite, you’ve might have experienced that your good old IDE might not support Grails 3 projects right out of the box.
You might be missing:
Here’s how I think you can fix some of these things.
As you regularly do with new Grails distributions is to add it in GGTS under Preferences > Groovy > Grails. But dang!…it doesn’t recognize the grails-3.0.x-directory you just unzipped a minute ago.
No worries! We have Gradle now.
Gradle is the new Grails 3 build system, in favor of Gant. If you’ve created e.g. the helloworld-application as used in the Getting Started section of the manual, you see a few files like build.gradle and gradle.properties.
Because of this we don’t need a specialized IDE plugin perse, since existing Gradle tooling can do the trick! So we skip adding a Grails 3 distribution and we look for…
It is possible that GGTS doesn’t know to import a Grails 3 project into your workspace, because of missing Gradle support. You can:
Generate Eclipse/GGTS…
gradlew eclipse.or install Gradle support
In GGTS your Grails 3 project is just a “regular” Gradle project.
The above screenshot is possibly an idealized view – it might as well that you have some red markers! I did.
Grails 3 comes with Groovy 2.4, and if you don’t have the correct version set, you get:
Groovy: compiler mismatch Project level is: 2.4 Workspace level is 2.3
Groovy compiler level expected by the project does not match workspace compiler level.
It’s similar as when you had to install Groovy 2.3 into GGTS 🙂 You can fix the project level to 2.3 but then you get
Groovy:Unexpected problem with AST transform: The Spock compiler plugin cannot execute because Spock 1.0.0-groovy-2.4 is not compatible with Groovy 2.3.10. For more information, see http://versioninfo.spockframework.org
You’ll have to get…
Assuming you don’t already have it, we have to install the Groovy Compiler 2.4 Feature into GGTS.
1. Go to Help > Install New Software and use the update site http://dist.springsource.org/snapshot/GRECLIPSE/e4.4/
2. Select the Groovy 2.4 compiler and Next.
3. If there’s a conflict, just press on – it’ll install Groovy 2.4 next to the other versions.
4. Continue all the way. Finish, restart.
5. Switch the compiler for the workspace. Go to Preferences > Groovy > Compiler and switch to 2.4.3.
Done.
Happy programming!
You don’t need to add all files in a Grails application- or plugin project to version control, because some of the files are derived (this means they can be re-created from source files) or they are generated for you locally as developer (and have nothing to do with the team) if you use IDEs such as Eclipse or Groovy/Grails Tool Suite (GGTS).
You should ignore the following files in version control:
| File or folder | Why not in version control? |
|---|---|
.project and .classpath |
Specific IDE (GGTS or Eclipse) generated derivations. |
.settings |
Specific IDE (GGTS or Eclipse) derivations and/or user settings. |
target |
Generated derived classes from sources |
target-eclipse |
Specific IDE (GGTS or Eclipse) generated derived classes from sources |
Generated files .project and .classpath contain developer-specific local paths which should not end up in version control. Former versions of Eclipse or GGTS could not deal with the absence of these files, and consequently failed to import any project without these.
Nowadays GGTS is able to detect this and fix it. You’ll get next dialog in this situation:
By answering Yes, aforementioned files will be re-generated.
This month has been interesting: on the 7th Groovy 2.3.0 has been released, followed up by Grails 2.4 a few days ago. Great work!
UPDATE: GGTS 3.6.0 M1 has been released, which already includes support for Groovy 2.3.
If you’re an Eclipse or Groovy/Grails Tool Suite (GGTS) user, you might want to install the Groovy/Eclipse Compiler to have the IDE make use of all the Groovy 2.3 features. Now if you’ve downloaded the latest GGTS version – which at the moment is 3.5.1 – and created a brand new Grails 2.4 project, the Markers view might have alerted you to the following:
Groovy: compiler mismatch Project level is: 2.3 Workspace level is 2.1 Groovy compiler level expected by the project does not match workspace compiler level.
Consequently, also 1 Java problem is reported about a java.lang.NoSuchMethodError in an AssetMethodTagLib.groovy of the new Asset Pipeline Plugin shipping with Grails 2.4
You might be tempted to follow the Quick Fix and set the project to 2.3 but the settings screen doesn’t allow you to select 2.3 yet.
Fix it by installing the Groovy Compiler 2.3 for Groovy/Eclipse.
http://dist.springsource.org/snapshot/GRECLIPSE/e4.3/After installation the compiler became the default for the entire workspace.
And you’re done. Problems are gone. Go work on your new Grails application 🙂
Sometimes using SpringSource Tool Suite (STS) e.g. version 2.3.2- which is based on Eclipse – startup hangs on various operations:
Initializing Java Tooling
Repository registry initialization
STS/Eclipse does not seem to respond to anything – the UI freezes and that’s it! I’ve had this on several occassions with no apparent cause on my part. Usually it has something to do with fiddling with (adding libraries to) the classpath and/or cleaning the project. Some users report Eclipse hangs at “Initializing Java Tooling” at 30% for 20-30 secs after which everything continues normally, but I don’t have that much luck 🙂 Continue reading “Eclipse “Initializing Java Tooling” hangs”
