2004-05-21 13:25:02 -04:00
|
|
|
#!/bin/sh
|
|
|
|
|
2004-05-21 13:28:07 -04:00
|
|
|
# This process assumes that maven-core-it-verifier has been built.
|
|
|
|
|
2004-09-09 07:13:12 -04:00
|
|
|
cp=../maven-core-it-verifier/target/maven-core-it-verifier-1.0.jar
|
2004-06-19 09:36:23 -04:00
|
|
|
|
2004-05-21 13:25:02 -04:00
|
|
|
verifier=org.apache.maven.it.Verifier
|
|
|
|
|
2004-09-09 07:13:12 -04:00
|
|
|
# TODO: need a consistent way to discover M2_HOME across this, bootstrap and m2 itself, as well as have a sensible
|
|
|
|
# default, and a way to override. There must be only one way.
|
|
|
|
# I like the idea of using the one in the path, or using -Dmaven.home to override
|
|
|
|
# The m2 shell script should not care what installation it is in - it should use the installation defined on the
|
|
|
|
# command line
|
2004-09-02 08:34:19 -04:00
|
|
|
|
2004-09-09 07:13:12 -04:00
|
|
|
jvm_args="$@"
|
2004-08-15 12:52:07 -04:00
|
|
|
|
2004-09-09 07:13:12 -04:00
|
|
|
if [ ! -z "$M2_HOME" ]; then
|
|
|
|
jvm_args="$jvm_args -Dmaven.home=$M2_HOME"
|
|
|
|
fi
|
2004-08-15 12:52:07 -04:00
|
|
|
|
2004-09-09 07:13:12 -04:00
|
|
|
java $jvm_args -cp "$cp" $verifier
|
2004-09-02 08:34:19 -04:00
|
|
|
|