There's no good diagnostics when do-component-build dynamically replaced the target Hadoop version. If the "to be replaced" version isn't present in the Oozie pom files, the error might not surfaced until later or at all: mvn will simply pull in incorrect versions of Hadoop libs. case in point: when doing something like this
sed will exit successfully even if no replacement took place. We need to guarantee to fail early.