Building geOrchestra

Building geOrchestra is generally not recommended, since we provide binaries.

Getting the sources

At this stage, if you don't have the geOrchestra sources, you need to download them:

git clone --recurse-submodules ~/georchestra

By default, this will always fetch the latest stable version.

Go grab some coffee in the mean time, or read on...

Use a mirror to fetch dependencies

In your ~/.m2/settings.xml, add a mirror:

<settings xmlns=""

Install the dependencies

You should install the required packages:

sudo apt-get install python-virtualenv openjdk-11-jdk ant ant-optional

Build the modules

Building your SDI is just few command-lines away.

cd ~/georchestra

Build Geonetwork

cd geonetwork
mvn -DskipTests clean install
cd ..

Build all modules (except GeoFence).

mvn -Dmaven.test.skip=true clean install

In case you only want to build one module or a collection, the syntax is a bit different:

mvn -Dmaven.test.skip=true -P-all,module1,module2 clean install

... where moduleX can be one of: analytics, cas, extractorapp, geonetwork, geofence, geoserver, geowebcache, header, console, mapfishapp, security-proxy.

Alternately, if you want to build all projects but one (say geowebcache-webapp):

mvn -Dmaven.test.skip=true --projects \!geowebcache-webapp clean install

As a result of the build process, you should find the geOrchestra artifacts into the subfolders of the ~/.m2/repository/org/ directory. Now, let's prepare the system to receive the webapps.

Are you having problems with the build ? Please ask on IRC freenode#georchestra. Note that if you're connecting to the internet through proxies, you need to tell maven how to reach public repositories.