I'm trying to figure out a good way to disable xtrace before leaving a script. These are all being executed by Wercker, a continuous integration and deployment SaaS.A previous script of mine has run enabling xtrace+ echo 7ad27e6b-75d9-4e72-a9a7-8b0d6796bd75 0source /pipeline/maven-9ea06b71-4392-4fec-ab5a-db7389b49cf2/run.sh < /dev/null+ source /pipeline/maven-9ea06b71-4392-4fec-ab5a-db7389b49cf2/run.sh++ set +o xtrace ## disabling here to keep other area's quiet...++ '[' -e settings.xml ']'++ SETTINGS=--settings=settings.xml++ mvn --update-snapshots --batch-mode -Dmaven.repo.local=/pipeline/cache --settings=settings.xml deploy...+ echo f5b142ac-a369-4166-967e-688d46c642c8 0here's my actual codeif [ -n $WERCKER_MAVEN_DEBUG ]; then    set -o xtrace    case $WERCKER_MAVEN_DEBUG in        [1-2]) env;;        [1-3]) DEBUG=--debug;;    esacfiif [ -e $WERCKER_MAVEN_SETTINGS ]; then   SETTINGS=--settings=${WERCKER_MAVEN_SETTINGS}fimvn --update-snapshots \    --batch-mode \    -Dmaven.repo.local=${WERCKER_CACHE_DIR} \    ${SETTINGS} ${DEBUG} \    ${WERCKER_MAVEN_GOALS}when I try to disable xtrace with set +o xtrace at the bottom of the file that changed the return to always be 0, and so even if maven was failing ci wasn't. I then tried to capture mavens return and call exit  ${STATUS} but this caused it to fail even when maven was succeeding with status 0. I think that had something to do with calling exit, not with how I was capturing the code.How can I disable xtrace after mvn has been executed while preserving mavens return status for the caller script?
How can I disable xtrace and preserve my exit code
shell;debugging;return status