Maven

Date	2010/03/25
Contact(s)	Mathieu, Francois
Last edited	Timestamp
Status	Draft
Assigned to release
Resources
Ticket

Overview

In Bolsena hacking event 2009, we decided to move from ant build to maven.

Maven structure

• GeoServer : no more embedded in GeoNetwork
• CSW client : removed
• jetty : via Maven (see Run the application)

Maven build

Build the application

mvn clean install

Packaging the application

GeoNetwork is distributed as WAR files (intermap.war and geonetwork.war) packaged by maven process.

Run the application

Maven plugins for Jetty or Cargo allows to quickly start the application after build.

War files

Publish war files created by maven to your favorite webapp directory (Tomcat, Jetty).

Maven plugin / Cargo

See : ​http://cargo.codehaus.org/

mvn cargo:start
mvn cargo:stop

Maven plugin / Jetty

mvn jetty:run

Current issue with jetty plugin is that we cannot run more than one application at a time (only geonetwork.war is started, not intermap.war).

Deploy the application

• TODO

Create an eclipse workspace

mvn eclipse:eclipse

Major changes

• OAI-PMH dependencies
• GAST :
  • Gast was using only the application path to load both resources and libs (from WEB-INF/lib). Add a libPath and an appPath.
  • Remove jetty and mckoi startup (see Open issues)
  • Current status : GAST could be used to create db (not mckoi ones) and load data once the catalogue is started.

Open issues

• GAST :
  • hardcoded classpath in MANIFEST
  • Gast start jetty to start mckoi and setup all.

Proposal Type

• Type: Architecture
• App: GeoNetwork
• Module: All

Links

• Email discussions:
  • ​http://n2.nabble.com/Re-switch-to-maven-tp4569552p4569552.html
  • ​http://n2.nabble.com/Maven-tp4009861p4009861.html
• IRC discussions:

Voting History

Proposal details

Backwards Compatibility Issues

None.

Risks

Participants

• Francois
• Mathieu
• Maven expert very welcomed !