Page History

...

The version I used is version 2.0.4.  I downloaded the binary distribution of Maven to get things started.    I use a Windows PC for development, so in my case this meant downloading the maven-2.0.4-bin.zip file, and unpacking this into my c:\apps\tools{color} directory to c:\apps\tools\apache\maven-2.0.4.  In subsequent steps I will refer to this directory as <maven home>.

A key concept in Maven is the repository that Maven uses when working with a project.  A base install of Maven starts with the core of Maven in the distribution, but the first time you actually use it "in anger" it will recursively examine all of the libraries that Maven/your application is dependent on, and it will download all of these files into a structured repository.  By default a new installation of Maven will use ~/.m2 as your repository - isolating the repository you use from others.  This is not the place to go into best practice for locating a Maven repository, but for the sake of this guide, I changed the location of the repository to point to a different location.

To do this, navigate to your <maven home>\conf directory, and open the file settings.xml.  Edit this file using a text editor - you will need to look for the tag <localRepository> which will be in a commented out section.  Uncomment this line, and edit it to point to somewhere you are comfortable with.  In my development environment, this is set up to point to a shared software repository on a network share, so my repository is set to <localRepository>s:/working/repository/<localRepository>.  In subsequent stpes I will refer to this as <maven repository home>

2. Download and Install Geronimo

The version I use is the Tomcat build of version 1.1.1.  I download the binary distribution of Geronimo.  I unpacked this into my standard directory structure to create c:\apps\tools\apache\geronimo-tomcat-j2ee-1.1

3. Get ServiceMix Source

The full suite of plugins/code required to integrate ServiceMix 3.0 with Geronimo 1.1 is not available within binary distribution of ServiceMix, so you will need to download the source files.  To get this, you will need a client for the source control tool Subversion on your machine.

...

It's best to create a clean directory to check out the source code.  This is because Subversion (like CVS) will create a directory (e.g. .svn) to hold meta information, and if you attempt to check out code from multiple locations (maybe not now - but ServiceMix might be the first of many) you could run into problems with meta data from one project overwriting another.  In my case I created the directory c:\working\external\servicemix.  In subsequent steps I will refer to this directory as <servicemix src home>.

Assuming you have TortiseSVN installed, right-click in the new directory (c:\working\external\servicemix) and select "SVN Checkout...".  When the dialog box appears, in the "URL of repository:" field enter "https://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0", and then press OK.  The Checkout dialog will appear and you *should* start to see a listing of the files/directories that are being checked out to your machine.

...

The build also uses a Geronimo Maven plugin to install the final product into Geronimo.  Maven essentially treats plugins like dependencies, and will download the plugins that are required.  This is configured through a file, and the version of the configuration that is included in the 3.0 source has a reference to a candidate-release repository version.  This needs to be changed to get Maven to use the correct version of the plugin.

Navigate to the <servicemix src home>\geronimo\servicemix\src\resources\META-INF directory, and open the file geronimo-plugin.xml in a text editor.  Search for the line

...