Description
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 -i.orig -e "s#2.0.2-alpha#${HADOOP_VERSION}#" ${WORKDIR}/hadooplibs/hadoop-distcp-2/pom.xml
sed will exit successfully even if no replacement took place. We need to guarantee to fail early.
Attachments
Attachments
Issue Links
- relates to
-
BIGTOP-837 Oozie 3.3.0 can't be build against Hadoop 2.0.3 or later
- Closed