For background on how to use the maven integration, see Groovy-Eclipse compiler plugin for Maven. This page describes how to get started with development on the project.
Clone the git repo:
The interesting components are in the
/extras folder. There are several projects located here:
There are several projects in the repository:
The are 2 maven artifacts required for compilation of groovy code in maven: groovy-eclipse-compiler and groovy-eclipse-batch. The first is just a thin wrapper around the compiler, and the second contains all of the files required to build. It is a bunch of Eclipse and Groovy-Eclipse jars unzipped and recombined into an uber-jar.
Historically, version numbers for both artifacts use a -01, -02, etc as a suffix. This is because groovy-eclipse-compiler versions track groovy-eclipse releases, but sometimes off-cycle releases are required. Similarly, groovy-eclipse-batch follows Groovy compiler releases
<!-- This is a sample settings.xml file for publishing maven artifacts to the codehaus maven repos --> <!-- This should go in your ~/.m2 directory --> <settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <servers> <server> <id>codehaus.org</id> <username>your_codehaus_username</username> <password>your_codehaus_password</password> </server> <server> <id>codehaus-nexus-snapshots</id> <username>your_codehaus_username</username> <password>your_codehaus_password</password> </server> <server> <id>codehaus-nexus-staging</id> <username>your_codehaus_username</username> <password>your_codehaus_password</password> </server> </servers> </settings>
This build process assumes that there is an existing Eclipse installation around and that the groovy-eclipse projects have been imported into a workspace and compile successfully. The build process will be copying class files from the bin folders of the projects.
groovy-eclipse-compiler-tests project contains regression tests. This project contains a set of sample projects that invoke the compiler in different ways. Run these often, even though they don’t test everything. It would be nice to merge this project with the groovy-eclipse-compiler project, but this hasn't happened yet.
To run the integrations tests:
groovy-eclipse-maven-tests project is just a play area where I try new things out.
There are none. The person who is responsible for this should be sacked...oh wait, that was me.
There is also a groovy-eclipse-compiler archetype, but it hasn’t been maintained in a looooong time. The project is
groovy-eclipse-quickstart. It would be good to move this project into the