[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478415#comment-13478415
]
Jarek Jarcec Cecho commented on HBASE-6929:
-------------------------------------------
Another possible solution would be to provide artifact hbase-test that would
have classifier either hadoop1 or hadoop2 based on for which version it was
compiled. This solution would be probably step back as for example hadoop was
using it in the past and has moved to classifiers, but it should be working
without need to have special version for testing artifact compiled against
hadoop2.
Jarcec
> 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
