[
https://issues.apache.org/jira/browse/BIGTOP-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14123329#comment-14123329
]
Andrew Purtell commented on BIGTOP-1427:
----------------------------------------
Upstream HBase munges the POM to produce -hadoop1 and -hadoop2 artifacts. We
will be ending this practice after HBase 0.98 by dropping support for Hadoop
1.x with HBase 1.0.
Bigtop builds HBase artifacts without this munging. I don't think Bigtop should
start doing that.
This does look like an issue with Flume's do-component-build script:
{code}
mvn -DskipTests -Dhadoop.profile=hbase-98 \
-Dhadoop2.version=$HADOOP_VERSION \
-Dhbase.version=${HBASE_VERSION}-hadoop2 \
clean install "$@"
{code}
That's only going to work if upstream put out the specified -hadoop2 artifact
in Maven central. It won't correspond with the local HBase artifacts Bigtop may
have built otherwise.
> HBase build should build hbase-***-hadoop2 by default
> -----------------------------------------------------
>
> Key: BIGTOP-1427
> URL: https://issues.apache.org/jira/browse/BIGTOP-1427
> Project: Bigtop
> Issue Type: Bug
> Reporter: stanley shi
>
> Flume is depending on hbase-**-hadoop2, but the hbase build is not providing
> this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
