[
https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741549#comment-13741549
]
stack commented on HBASE-9213:
------------------------------
[~sershe] np.
How you mean publishes the old stuff? You mean into your local repo? Yeah,
that is true. Regards what to consume, isn't that easy. Up in apache we have
hadoop1 and hadoop2 tgzs or in mvn we have hbase-X.Y.Z-hadoop1 and
hbase-X.Y.Z-hadoop2 only. See http://people.apache.org/~stack/hbase-0.95.2RC0/
and
https://repository.apache.org/content/repositories/releases/org/apache/hbase/hbase/
for example based off hbase-0.95.2.
> create a unified shim for hadoop 1 and 2 so that there's one build of HBase
> ---------------------------------------------------------------------------
>
> Key: HBASE-9213
> URL: https://issues.apache.org/jira/browse/HBASE-9213
> Project: HBase
> Issue Type: Brainstorming
> Components: build
> Reporter: Sergey Shelukhin
> Fix For: 0.96.0
>
>
> This is a brainstorming JIRA. Working with HBase dependency at this point
> seems to be rather painful from what I hear from other folks. We could do the
> hive model with unified shim, built in such manner that it can work with
> either version, where at build time dependencies for all 2-3 versions are
> pulled and the appropriate one is used for tests, and when running HBase you
> have to point at Hadoop directory to get the dependencies. I am not very
> proficient at maven so not quite certain of the best solution yet.
--
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
