To build the Geronimo Eclipse Plugin (GEP) from source you need to have the following prerequisites installed.
- Apache Maven 2.2.1+
- Subversion 1.5.4+
- Sun JDK 6.0+ downloads
- Add the bin directories of maven and subversion to system variable Path.
You can also change the default location of m2repo by modifying <MAVEN_HOME>/conf/settings.xml and modify the following tag
Getting the source code
- Create a directory gep in the root location.
It is strongly recommended that you use a small directory name for the source code download. At times there have been issues due to long path.
- Open a command prompt and change gep directory created before. Run the following command to start downloading the source.
- Subversion will start downloading the source and the command window will show the progress information.
- On successful download you can see the revision number for the downloaded source.
- Modify heap settings for JVM as follows.
The following environment variable needs be set to properly configure the JVM to meet memory requirements.
MAVEN_OPTS="-Xms512m -Xmx512m -XX:MaxPermSize=256m"
On Windows use the following command to set the environment variable (note that double quotes should not be used):
set MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128m
- Change to the trunk directory of the source you have downloaded and run the following command
- Once done various dependencies will be downloaded to your m2 repository. If you are building GEP for the first time it may take considerable time.
- On the success of build you can see a Build Successful message on the command prompt.
You do not need to manually download Eclipse or the web tools project to build. This is taken care of for you automatically during the build process. You can find the downloads at
Other Maven options
Skip TestAt times your build may fail due to test case failure. You can skip the test by running the following command
If you want to run integration test against GEP source code, use mvn clean install -Ptestsuite to build the GEP. But be aware that this command could result in GEP build failure because lots of jar files on which GEP depends are not available in the maven central repository any more, and another reason is that source code in trunk is not stable yet.