[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478518#comment-13478518
]
Enis Soztutar commented on HBASE-6929:
--------------------------------------
bq. 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
We should not do this for h1, since that would break maven compatibility that
our previous artifacts (0.94.0, 0.94.1, etc) was released with artifact name
hbase, and classifier tests. However, maybe we can do it for hadoop2, not sure
how easy it would be to create hbase-tests artifact with classifier hadoop-2.
Since maven-deploy hardcodes "tests" classifier, this might not be possible at
all.
bq. Long time ago I filed HBASE-4850 but haven't had much time to devote to it
since then.
What versions of hadoop? If between hadoop1 and hadoop2, then I don't think we
can resolve this easily without creating a shim layer for pretty much
everything.
See:
http://dbeech.github.com/hadoop-api-evolution.html
> 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
