Building

Building GeoBatch

---

You need maven, at least version 2.1.0.

Including actions

---

There's a profile for every Action implemented in GeoBatch. If you want all Actions to be included, you may use the all_actions var:

mvn install

Actions' sample flows

---

Actions may provide one or more sample flows.

They are located in

GB_DIR/src/actions/ACTIONPACKAGE/src/main/resources/data

This dir will not be included in the standard jar (e.g. {{{gb-action-geotiff-0.9-SNAPSHOT.jar}}} ) but will be put in a jar of its own (e.g. {{{gb-action-geotiff-0.9-SNAPSHOT-flowdata.jar}}}). The ''flowdata'' will then be expanded by maven in the war's {{{WEB-INF/data dir}}}.

Sample flow: a tech note

---

https://geosolutions-trac.sourcerepo.com/geosolutions_geobatch/browser/src/actions/pom.xml Here the maven-jar-plugin is configured in order to:

• exclude the data/ dir in the base jar;
• create the flowdata jar containing only the {{{data/}}} dir.

Note that this plugin behaviour is inherited by the maven submodules of the {{{Action}}} module. Should you create an Action outside this module, you'll have to redefine the plugin behaviour exacly as described.

[https://geosolutions-trac.sourcerepo.com/geosolutions_geobatch/browser/src/web/pom.xml Here ], in a quite verbose way, the {{{maven-dependency-plugin}}} is used to expand, Action by Action, the ''flowdata'' jars into the proper directory.

Future improvements

---

We have to develop a '''maven archetype''' that will allow you to create a maven module for a GeoBatchAction.

As a second step, we need to sort out a way in order to include external artifacts in an uncustomized GeoBatch source tree: use case:

1. Create an Action module, outside the !GeoBatch source tree, using the proper maven archetype; 1. implement and build that Action; 1. build !GeoBatch from an uncustomized source tree, asking maven to include in the final WAR also the newly created Action.

Building all GeoBatch modules in one shot

---

Within the Geobatch src dir:

mvn clean install -Dall