If the overlord-common.sh is the definite way how the commons will be installed (if it won't be part of the fuse-patch mechanism) then the script needs to be updated to be able to work when called from anywhere.

Right now it is required to be ran from <eap_home> as ./scripts/overlord/rtgov/install-overlord.sh as it supplies `pwd` as "path" argument into the ant script.

This modification work in my env and I am able to run it from anywhere:

10:10:46 ~/work/rtgov/jboss-eap-6.4/scripts/overlord/rtgov$ cat install-overlord.sh 
#!/bin/sh
SCRIPT_HOME=`dirname $(readlink -f $0)`
EAP_HOME=`readlink -f ${SCRIPT_HOME}/../../..`
ANT_HOME=`readlink -f ${EAP_HOME}/lib`

java -Dant.home=${ANT_HOME} -Dpath=${EAP_HOME} -Dappserver.id=jboss-eap-64 -cp ${ANT_HOME}/ant-launcher-1.8.3.jar org.apache.tools.ant.launch.Launcher -f ${SCRIPT_HOME}/platforms/jboss-eap-64/all/build.xml install