Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 57783 invoked from network); 3 Jan 2010 22:39:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Jan 2010 22:39:15 -0000 Received: (qmail 11773 invoked by uid 500); 3 Jan 2010 22:39:15 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 11727 invoked by uid 500); 3 Jan 2010 22:39:15 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 11717 invoked by uid 99); 3 Jan 2010 22:39:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Jan 2010 22:39:15 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Jan 2010 22:39:14 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7EB7E234C045 for ; Sun, 3 Jan 2010 14:38:54 -0800 (PST) Message-ID: <527516803.12811262558334504.JavaMail.jira@brutus.apache.org> Date: Sun, 3 Jan 2010 22:38:54 +0000 (UTC) From: "stack (JIRA)" 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796042#action_12796042 ] stack commented on HBASE-1433: ------------------------------ .bq I have not. That is tricky because it pulls the latest snapshot across three different projects ( core . hdfs, mapreduce ) . Also - one of the hdfs snapshots (0.21 ) seemed to pull (0.22) from core. We also need to have some sort of conflict resolver specific to core / hdfs / mapreduce to prevent similar conflicts ( as opposed to the default one ). A custom conflict resolver sounds like loads of fun (smile). If a 0.21 hdfs snapshot is pulling in 0.22, that sounds well broke. How about putting up a patch that leaves the hadoop stuff as checkins and not pull these from a repo just yet (or, maybe if you just check in commons, and pull the other two, does that help)? I suggest this because the patch as is where it moves the bulk of the jar includes to instead be ivy pulls is a nice fat contribution. It also gets you what you need, an updated lucene? Good stuff on the fact that jsp-2.1 is being pulled already and jersery-json is a transitive include. > 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.