This document describes how to build a deployable EAR file from the gateway source code using Eclipse
In this tutorial, we assume that you have installed Eclipse and have used the Subclipse plugin to check out the Gateway source. The Maven plugin is also required.
It is important to note that you only need the target modules you wish to build downloaded from the repository. When a Maven command is issued to build the module, Maven will acquire the dependencies not stored locally from our Gateway repository at OSU.
In order to build the EAR file you *must* have the "config" directory from the repository present in the same directory as the gateway-ear-jboss module.
If any modules have been modified locally, the local Maven repository must be cleaned out to allow modified modules to replace the ones taken from the online repository. This is accomplished by cleaning out one of two directories:
On Linux systems remove the directory:
/home/<username>/.m2/repository/net/sf/gateway
On Windows systems remove the directory:
C:\Documents and Settings\<username>\.m2\repository\net\sf\gateway
All the standard Maven goals such as install, clean, and test are available with the Maven plugin. These are accessed by navigating to any pom.xml, (these exist for every module), and right clicking and selecting Run As .
To use state specific configuration files or host specific configuration files you need to activate different build profiles. Documentation on how to do this along with some examples are listed on the profiles page.
To run other Maven goals such as site, select Maven build... and then enter them into the Goals field. Give the new configuration a name and when you need to run it again, navigate to Run on the Eclipse tool bar and then External Tools and all your custom goals should be listed.