[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468338#comment-13468338
]
Enis Soztutar commented on HBASE-6929:
--------------------------------------
bq. Officially 0.96 supports hadoop2, not 0.94
I saw a bunch of fixes for hadoop-2.0, but did not check whether 0.94 it works.
Let me go over the fixes that went in to see whether 0.94 can also officially
support 2.0. Although not officially production-ready, 0.94 builds with
hadoop-2.0, and there are some interest in downstream projects to build and run
tests with h2, publishing the artifacts might be justified.
bq. How would we publish the different jars to mvn repo?
We do not need to break the current setup for h1. Since the binaries are
different we can publish h2 artifacts with either naming it smt like
hbase-hadoop2-X.X.X.jar, or using maven classifiers.
Agreed that this is ugly, but if we do not publish the artifacts, downstream
projects cannot easily consume hbase jars build with hadoop-2.0 in their
hadoop-2.0 profiles.
> Publish Hbase 0.94 artifacts build against hadoop-2.0
> -----------------------------------------------------
>
> Key: HBASE-6929
> URL: https://issues.apache.org/jira/browse/HBASE-6929
> Project: HBase
> Issue Type: Task
> Components: build
> Affects Versions: 0.94.2
> Reporter: Enis Soztutar
>
> Downstream projects (flume, hive, pig, etc) depends on hbase, but since the
> hbase binaries build with hadoop-2.0 are not pushed to maven, they cannot
> depend on them. AFAIK, hadoop 1 and 2 are not binary compatible, so we should
> also push hbase jars build with hadoop2.0 profile into maven, possibly with
> version string like 0.94.2-hadoop2.0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
