Skip to content
Ian Mayo edited this page Aug 16, 2016 · 4 revisions

Here is the command line steps to perform a Maven build (from the top level Limpet folder):

mvn clean verify site -U -B -fae

The code coverage outputs will be in target/site sub-folders of each project. The Travis-hosted deploy operation pulls the separate reports together.

Overcoming out of memory problems

For Linux Java 7:

export MAVEN_OPTS="-Xmx1024M -Xms256M -XX:PermSize=128M -XX:MaxPermSize=256M"

is on Linux. For Java 8, we would use:

export MAVEN_OPTS="-Xmx1024M -Xms256M"

other options are deprecated in Java 8.

On Windows, it is

set MAVEN_OPTS=-Xmx1024M -Xms256M -XX:PermSize=128M -XX:MaxPermSize=256M

(set instead of export and without ") or define MAVEN_OPTS in Windows Environment.

Maven Tasks as Eclipse external task

Maven build

  • Location: /usr/bin/mvn
  • Working Directory: /Users/xxx/git/limpet/
  • Arguments: clean verify -DskipTests