Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9ADB311ADD for ; Fri, 27 Jun 2014 12:04:31 +0000 (UTC) Received: (qmail 95368 invoked by uid 500); 27 Jun 2014 12:04:31 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 95290 invoked by uid 500); 27 Jun 2014 12:04:31 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 95278 invoked by uid 99); 27 Jun 2014 12:04:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2014 12:04:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.213.42 as permitted sender) Received: from [209.85.213.42] (HELO mail-yh0-f42.google.com) (209.85.213.42) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2014 12:04:26 +0000 Received: by mail-yh0-f42.google.com with SMTP id i57so2980182yha.29 for ; Fri, 27 Jun 2014 05:04:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=STFSyYt4yJS5fZBQp7oxN254ip7y5wgMPPM4JhT9hik=; b=t/zeezA5MsLYVLxp0aDAURmfB0FREkJqRNGuu25zL9+Evl/8Nf8es1MkFngqaTD3zs +x0xw5zi6QOB83XUt6Q8Gs7RP4s4OUFded8rtCLQQVv334bloSA9Ced0IiAev0IQHCeV Pl8TmXJmzvDXZNwjvNf1ZK7WYAKNYv0PtZ4GrRDhHVlcWiYLf2kd5kkXqXUmgfsvPkZ1 Z9ZSHpjyHRK9/ImCfmIYVEASLPOck5sV3uHkUSVLUh4aH1QcqSoLduDvLvmeoCvl6jDr hLp5sKMNubFy6HW84mpnnytL43sAT0EtmuNW7DLYT9TX3n82DVYdhA9q1+p5VSVyDWpx E9IA== MIME-Version: 1.0 X-Received: by 10.236.20.114 with SMTP id o78mr31772022yho.91.1403870642255; Fri, 27 Jun 2014 05:04:02 -0700 (PDT) Received: by 10.170.55.137 with HTTP; Fri, 27 Jun 2014 05:04:02 -0700 (PDT) In-Reply-To: <20140627044319.GU27913@boudnik.org> References: <20140617184024.GI27913@boudnik.org> <20140618033331.GO27913@boudnik.org> <20140627044319.GU27913@boudnik.org> Date: Fri, 27 Jun 2014 05:04:02 -0700 Message-ID: Subject: Re: HBase 0.98.x dependency problems From: Ted Yu To: "dev@hbase.apache.org" Content-Type: multipart/alternative; boundary=089e01635714f13b0904fcd01a53 X-Virus-Checked: Checked by ClamAV on apache.org --089e01635714f13b0904fcd01a53 Content-Type: text/plain; charset=UTF-8 Thanks for finding this issue, Cos. I opened HBASE-11422 and attached a patch there - there is no dependency on 2.2.0 if -Dhadoop-two.version=2.3.0 is specified. Cheers On Thu, Jun 26, 2014 at 9:43 PM, Konstantin Boudnik wrote: > Weird... running > mvn install dependency:tree -Dhadoop-two.version=2.3.0 > keeps pulling in 2.2.0 for test artifacts. An easy way to reproduce it is > to > wipe out clean hadoop 2.2.0 artifacts from ~/.m2 as well as 0.98.2* (if > installed) and then run the command above. Something like this can be seen: > > [INFO] +- org.apache.hbase:hbase-shell:jar:0.98.2:compile > [INFO] | +- org.apache.hbase:hbase-prefix-tree:jar:0.98.2:runtime > [INFO] | +- com.yammer.metrics:metrics-core:jar:2.1.2:compile > [INFO] | +- org.jruby:jruby-complete:jar:1.6.8:compile > [INFO] | +- org.apache.hadoop:hadoop-client:jar:2.3.0:compile > [INFO] | | +- > org.apache.hadoop:hadoop-mapreduce-client-app:jar:2.3.0:compile > [INFO] | | +- org.apache.hadoop:hadoop-yarn-api:jar:2.3.0:compile > [INFO] | | \- > org.apache.hadoop:hadoop-mapreduce-client-jobclient:jar:2.3.0:compile > [INFO] | +- org.apache.hadoop:hadoop-hdfs:jar:2.3.0:compile > [INFO] | | \- commons-daemon:commons-daemon:jar:1.0.13:compile > [INFO] | \- org.apache.hadoop:hadoop-hdfs:test-jar:tests:2.2.0:compile > > I have fixed a problem with site target, but still see this... > > Any ideas are very appreciated! Thanks. > Cos > > > On Tue, Jun 17, 2014 at 08:33PM, Konstantin Boudnik wrote: > > Thank you very much Ted - that helped beautifully! I think the build > system > > becomes a product on its own :) > > > > Regards, > > Cos > > > > On Tue, Jun 17, 2014 at 12:40PM, Ted Yu wrote: > > > Have you tried the following command ? > > > > > > mvn dependency:tree -Dhadoop-two.version=2.3.0 > > > > > > The output of the above has 2.3.0 as the dependency. > > > > > > Cheers > > > > > > > > > On Tue, Jun 17, 2014 at 11:40 AM, Konstantin Boudnik > wrote: > > > > > > > Guys, > > > > > > > > I have noticed an interesting problem with HBase 0.98 line. I have > ended > > > > up with > > > > a crappy Hadoop 2.2.0 artifacts in my local M2 cache - don't ask me > how > > > > that > > > > happen ;( - which causes compilation problems in HBase. And that > brought > > > > this > > > > whole issue into the light. Here's the essence of it: > > > > > > > > while running for hbase-server module > > > > % mvn dependency:tree -Dhadoop.version=2.3.0 > > > > I am getting a reference to hadoop 2.2.0 > > > > > > > > [INFO] +- org.apache.hadoop:hadoop-common:jar:2.2.0:compile > > > > .. > > > > [INFO] +- org.apache.hadoop:hadoop-auth:jar:2.2.0:compile > > > > [INFO] +- org.apache.hadoop:hadoop-client:jar:2.2.0:compile > > > > > > > > This only happens for 0.98. On master the reference goes to 2.4.0 > > > > The problem here is that -Dhadoop.version is being seemingly > ignored, which > > > > might lead to binaries with dependencies inconsistent with what it > was > > > > built > > > > against. I am not sure if this had came up before, but certainly > would > > > > appreciate the community's input, if any. > > > > > > > > Thanks a lot! > > > > -- > > > > Take care, > > > > Cos > > > > > > > > > --089e01635714f13b0904fcd01a53--