Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1087128313.27391262635434445.JavaMail.jira@brutus.apache.org>
Date: Mon, 4 Jan 2010 20:03:54 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1433) Update hbase build to match core,
 use ivy, publish jars to maven repo, etc.
In-Reply-To: <1713437109.1242669525634.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-1433:
------------------------------

@ Kay Kay: Good stuff. Seems like we should just commit the pom changes over in mapreduce-1352 (though it looks like the pom change may have broken at least one unit test) and same for hdfs-869.  Whats there is just broke.   Is there an issue up in hadoop for fixing the dynamic link issue or do you think addressing the mapreduce-1352 and hdfs-869 will take care of it?

> Update hbase build to match core, use ivy, publish jars to maven repo, etc.
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-1433
>                 URL: https://issues.apache.org/jira/browse/HBASE-1433
>             Project: Hadoop HBase
>          Issue Type: Task
>    Affects Versions: 0.20.2
>            Reporter: stack
>         Attachments: HBASE-1433.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.