Groovy-Eclipse supports both the 1.8 compiler and the 1.7 compiler for Groovy. However, due to Groovy-Eclipse's tight integration with the compiler, only one version of the compiler can be used in the workspace at one time. Switching compiler levels requires a restart.
By default, Groovy-Eclipse comes installed with a 1.7 compiler. This is the compiler that is installed when you select the Groovy-Eclipse feature from the Groovy update site:
If you would like to install the 1.8.x compiler (currently 1.8.RC2), then you must add one of the development update sites to your install manager:
To perform the installation, you must install the latest dev snapshot of Groovy-Eclipse as well as the Groovy Compiler 1.8 feature (the SDK and m2eclipse integration are optional):
Then click Next > and follow the instructions to complete the installation. A restart is necessary.
Switching compiler levels
You can switch between the 1.7 and 1.8 compilers for your Eclipse workspace in the Preferences -> Groovy -> Compiler page:
Simply click the button and Eclipse will restart automatically. The hyperlink shown on the preference page will navigate you to this wiki page.
Uninstalling the 1.8 compiler
You can uninstall the 1.8 compiler through the update manager. In the lower right corner of the update manager, there is a link that says What is already installed?:
Click the link, select the Groovy 1.8 compiler, and then click Uninstall...:
Then follow the instructions and restart to complete the uninstallation process. Once the 1.8 compiler is uninstalled, you can follow the steps above to reinstall it.
Switching from outside of Eclipse
If you cannot switch compilers from the Groovy Compiler preference page, follow the instructions to perform the switch from outside of Eclipse:
- Shut down Eclipse
- Go to eclipse/configuration/org.eclipse.equinox.simpleconfigurator
- Make a backup copy of bundles.info
- Open bundles.info in a text editor
- Find the line for org.codehaus.groovy_1.8 and delete
- Restart eclipse
To re-enable the 1.7 compiler, simply reinstate the backed up copy of bundles.info.