[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468314#comment-13468314
]
stack commented on HBASE-6929:
------------------------------
[~enis] Officially 0.96 supports hadoop2, not 0.94. How would we publish the
different jars to mvn repo? Those built for h1 and those for h2? The artifact
is hbase-X.X.X.jar? You suggest adding a hadoop1 and hadoop2 to the name?
Even then, we're breaking the mvn model of an artifact per module. Maybe
hbase-X.X.X.jar becomes a meta jar under which you can slot in hbase-h1 or
hbase-h2... but that sounds like ugly work w/ an explosion in hbase maven
modules?
> 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
