[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485557#comment-13485557
]
stack commented on HBASE-6929:
------------------------------
I don't think hbase-4850 possible as of this writing. It may become so by the
time we release (you might just have to shuffle the CLASSPATH if we move all h1
and h2 mannerisms successfully back into their respective compatibility
modules). Meantime, messing w/ version string seems the way to go.
Is there a hurry on solving this one? I'd like to do a bit of testing and
leave the decision on what we'll publish till close to release if that is ok w/
bigtop and other downstreamers.
> 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
> Attachments: 6929.txt, hbase-6929_v2.patch
>
>
> 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
