[
https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184882#comment-16184882
]
Josh Elser commented on HBASE-17441:
------------------------------------
I had a thought that maybe the issue isn't with the Maven build at all, but
with Yetus. Found this:
{noformat}
diff --git a/dev-support/hbase-personality.sh b/dev-support/hbase-personality.sh
index b7a2f9730c..c58e47e634 100755
--- a/dev-support/hbase-personality.sh
+++ b/dev-support/hbase-personality.sh
@@ -267,8 +267,8 @@ function hadoopcheck_rebuild
echo_and_redirect "${logfile}" \
"${MAVEN}" clean install \
-DskipTests -DHBasePatchProcess \
- -Dhadoop-three.version="${hadoopver} \
- -Dhadoop.profile=3.0"
+ -Dhadoop-three.version="${hadoopver}" \
+ -Dhadoop.profile=3.0
count=$(${GREP} -c '\[ERROR\]' "${logfile}")
if [[ ${count} -gt 0 ]]; then
add_vote_table -1 hadoopcheck "${BUILDMODEMSG} causes ${count} errors
with Hadoop v${hadoopver}."
{noformat}
[~busbey], thoughts? Perhaps some aggressive quoting is screwing up the parsing.
> precommit test "hadoopcheck" not properly testing Hadoop 3 profile
> ------------------------------------------------------------------
>
> Key: HBASE-17441
> URL: https://issues.apache.org/jira/browse/HBASE-17441
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 2.0.0
> Reporter: Sean Busbey
> Assignee: Josh Elser
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17441.0.patch
>
>
> HBASE-14061 made a change that caused building against hadoop 3 to fail, but
> the hadoopcheck precommit test gave the change a +1.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
