HBASE-7168 ADD in the script called 'hbase', we don't check for errors when generating the classpath with mvn

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1414868 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
eclark 2012-11-28 19:05:15 +00:00
parent c4ff575b89
commit e6053a6160
1 changed files with 5 additions and 2 deletions

View File

@ -156,13 +156,16 @@ add_maven_deps_to_classpath() {
f="${HBASE_HOME}/target/cached_classpath.txt" f="${HBASE_HOME}/target/cached_classpath.txt"
if [ ! -f "${f}" ] if [ ! -f "${f}" ]
then then
${MVN} -f "${HBASE_HOME}/pom.xml" package dependency:build-classpath -DskipTests -Dmdep.outputFile="${f}" $MAVEN_OPTS &> /dev/null #we need hbase-it to always be the last module run. since it has the largest classpath
modules=`find hbase-* -type f -name 'pom.xml' |sed 's#\(.*\)/.*#\1#' | sed '/hbase-it/d' |sort -u | paste -s -d , -`
modules="${modules},hbase-it"
${MVN} -f "${HBASE_HOME}/pom.xml" package dependency:build-classpath -DskipTests -Dmdep.outputFile="${f}" -pl "${modules}" &> /dev/null
if [ $? -ne 0 ] if [ $? -ne 0 ]
then then
#delete the file, maven writes it even on failure. Keeping it would breaks the caching mechanism the next time we call the script #delete the file, maven writes it even on failure. Keeping it would breaks the caching mechanism the next time we call the script
rm -rf "${f}" rm -rf "${f}"
echo "The maven command used to generate the classpath failed, please check your environment." echo "The maven command used to generate the classpath failed, please check your environment."
echo "Maven command was: ${MVN} -f '${HBASE_HOME}/pom.xml' package dependency:build-classpath -DskipTests -Dmdep.outputFile='${f}' $MAVEN_OPTS" echo "Maven command was: ${MVN} -f '${HBASE_HOME}/pom.xml' package dependency:build-classpath -DskipTests -Dmdep.outputFile='${f}' -pl '${modules}'"
exit 1 exit 1
fi fi
fi fi