Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 15 Aug 2013 01:14:50 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12663565.1376451406985.69652.1376529290357@arcas>
In-Reply-To: <JIRA.12663565.1376451406985@arcas>
References: <JIRA.12663565.1376451406985@arcas>
Subject: [jira] [Commented] (HBASE-9213) create a unified shim for hadoop 1
 and 2 so that there's one build of HBase
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740528#comment-13740528 ] 

Elliott Clark commented on HBASE-9213:
--------------------------------------

https://repository.apache.org/content/groups/snapshots/org/apache/hbase/hbase-common/


I think that there will be two different versions of hbase-common
                
> 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