Build Notes for using Eclipse (Spring Tool Suite version):

Checkout trunk from svn. 
cd ArrowManualArtifacts and run 'mvn install'  (needs ant to be installed) 
Alternatively, import the project to Eclipse, and run Maven Install.
Create a new workspace in Eclipse; note that this needs to be outside of the checkout area. 
From Eclipse, use “Import:Existing Maven Project” to bring projects into the workspace. 
The trunk/arrow-mvn-init project installs a root pom for Arrow: do one of the following ; From the command line in the arrow-mvn-init directory run ‘mvn install’. Import arrow-mvn-init into your Eclipse workspace and Run As:mvn install. 
The maven project arrow-mvn-all will build all of the arrow maven projects, and ‘mvn install’ needs to be run on this project to ensure that all maven project dependencies are available locally.
 

 

Notes regarding Eclipse and Maven:

We prefer to use maven based projects, and we like the support that the Spring Tool Suite IDE gives us for development.

Maven has as its primary project specification a pom.xml file. Eclipse uses .project and .classpath as its primary project specification.

In our development, the pom.xml takes precedence, and files and and directories that are created automatically in the build process should not be committed to svn. This includes the .project and .classpath files, as well as the target/ directory. However, in order for Eclipse to be happy each user will have .project and .classpath, which initially are created on import from the pom.xml into the Eclipse workspace. I think they are updated when the pom.xml file is modified as well, and they can be forcefully regenerated by choose the ‘Maven:Update Project Configuration’ from the Eclipse Project Explorer context menu.