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 E0FEC10751 for ; Tue, 29 Apr 2014 23:27:40 +0000 (UTC) Received: (qmail 26685 invoked by uid 500); 29 Apr 2014 23:27:38 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 26518 invoked by uid 500); 29 Apr 2014 23:27:38 -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 26509 invoked by uid 99); 29 Apr 2014 23:27:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Apr 2014 23:27:38 +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 (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.216.51 as permitted sender) Received: from [209.85.216.51] (HELO mail-qa0-f51.google.com) (209.85.216.51) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Apr 2014 23:27:32 +0000 Received: by mail-qa0-f51.google.com with SMTP id ih12so905029qab.38 for ; Tue, 29 Apr 2014 16:27:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=chhlySSV/RHUYtR/y9EAzfo6Va9apDAmTKmOjL6YwWY=; b=l+BmThJ6Y3lRHopyy2R7p2DflfLasUnP9Y57hddZeWp1/tlsGfMCrAzw7UlncIsuxE DxFygEwq3KlDI7IW5I8J1y/KzjtR5YfLa+GA2FuPOucZ2CVquLz4ifig5f7cFgweHw+h LsDvhIxcQl1osAJwrcV0AgiGiB1Z4bfDPSen32SCrIEwQavX/yxjCbBH1Pm6f9GVAyhd 4d+5CV1AxDSKxUG3KNGID7E6F3Ov5gm3q5vBYMpPwF6HW5Bwvb6Ak9p4MFullzuGtWhB ck0EmU3uS5Xy0hpjwRxEmQwjH4VsMPG0XSuwc1Clc0YLnw7Sj2+hxA+OjUygJG0s+wzu aLmA== MIME-Version: 1.0 X-Received: by 10.140.81.48 with SMTP id e45mr709158qgd.99.1398814032049; Tue, 29 Apr 2014 16:27:12 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.96.183.230 with HTTP; Tue, 29 Apr 2014 16:27:11 -0700 (PDT) In-Reply-To: <20140429231851.GC6333@boudnik.org> References: <20140422231718.GP22142@boudnik.org> <20140423022649.GS22142@boudnik.org> <20140429213832.GY6333@boudnik.org> <20140429215422.GZ6333@boudnik.org> <20140429231851.GC6333@boudnik.org> Date: Tue, 29 Apr 2014 16:27:11 -0700 X-Google-Sender-Auth: U-LdJPahoIIUkYJNDQ-o5YErUZk Message-ID: Subject: Re: 0.98.1 has stopped building [Was: What happened to tar.gz assembly in 0.98?] From: Stack To: HBase Dev List Content-Type: multipart/alternative; boundary=001a11c123f27cd7dc04f836c523 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c123f27cd7dc04f836c523 Content-Type: text/plain; charset=UTF-8 On Tue, Apr 29, 2014 at 4:18 PM, Konstantin Boudnik wrote: > Do you guys think it'd make sense to find site:run to install phase? It wouldn't fly. You'd piss off everyone as they wait on javadoc and doc targets every time they make small change. Site is intentionally broken off an explicit goal unhooked from maven lifecycle for this reason. Ditto assembly for similar but also more convoluted reasons. St.Ack > This way > - in theory at least - site will always be executing install first? It > might > be too small of an issue though which might be totally workarounded with > two > sequential maven runs. > > e, Apr 29, 2014 at 02:48PM, Andrew Purtell wrote: > > > Ah, and if I read to the end ( sorry - sometimes don't do that when > annoyed > > > - unrelated to this :-) ), then indeed you did clean ~/.m2 and then > > > attempted a list of targets including site. > > > > > > Install jars to the local Maven cache before invoking javadoc or site > > > targets. > > > > > > > > > On Tue, Apr 29, 2014 at 2:44 PM, Andrew Purtell > wrote: > > > > > > > Is this because we frob the Maven versions after rolling the source > > > > tarball? See https://hbase.apache.org/book/releasing.html > > > > > > > > Do 'mvn -DskipTests clean install' first, then something that pulls > in > > > > javadoc or site targets and you should be fine. My guess is you did > that at > > > > one point, then moved to a different box or somehow wiped out local > 0.98.1 > > > > artifacts in your ~/.m2. > > > > > > > > > > > > On Tue, Apr 29, 2014 at 2:38 PM, Konstantin Boudnik >wrote: > > > > > > > >> This is a bit weird, but since last night I can't build 0.98.1 > anymore > > > >> because > > > >> of the following error: > > > >> > > > >> [ERROR] Failed to execute goal > > > >> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) > on > > > >> project > > > >> hbase: failed to get report for > > > >> org.apache.maven.plugins:maven-javadoc-plugin: > > > >> Failed to execute goal on project hbase-server: Could not resolve > > > >> dependencies > > > >> for project org.apache.hbase:hbase-server:jar:0.98.1: The following > > > >> artifacts > > > >> could not be resolved: org.apache.hbase:hbase-common:jar:0.98.1, > > > >> org.apache.hbase:hbase-protocol:jar:0.98.1, > > > >> org.apache.hbase:hbase-client:jar:0.98.1, > > > >> org.apache.hbase:hbase-prefix-tree:jar:0.98.1, > > > >> org.apache.hbase:hbase-common:jar:tests:0.98.1, > > > >> org.apache.hbase:hbase-hadoop-compat:jar:0.98.1, > > > >> org.apache.hbase:hbase-hadoop-compat:jar:tests:0.98.1, > > > >> org.apache.hbase:hbase-hadoop2-compat:jar:0.98.1, > > > >> org.apache.hbase:hbase-hadoop2-compat:jar:tests:0.98.1: Could > not find > > > >> artifact org.apache.hbase:hbase-common:jar:0.98.1 in apache > release > > > >> (https://repository.apache.org/content/repositories/releases/) > -> > > > >> [Help 1] > > > >> > > > >> Naturally, such artifacts aren't available in the aforementioned > repo, > > > >> because > > > >> only *-hadoop1 and *-hadoop2 versions are there. I am using the > same maven > > > >> command as before. But even the standard release command > > > >> mvn clean install -DskipTests site assembly:single -Prelease > > > >> > > > >> doesn't work anymore. I am building with clean ~/.m2, if it makes > any > > > >> difference. Anyone here has a similar experience? > > > >> > > > >> Thanks in advance, > > > >> Cos > > > >> > > > >> On Tue, Apr 22, 2014 at 07:26PM, Konstantin Boudnik wrote: > > > >> > Right, thanks! Also, it moved + plus set of artifacts got > changed. No > > > >> matter - > > > >> > I got the packaging working again, so once HBase has 0.98.2 out > of the > > > >> door it > > > >> > will be right there in Bigtop 0.8.0. Appreciate the help, guys! > > > >> > > > > >> > Cos > > > >> > > > > >> > On Tue, Apr 22, 2014 at 04:20PM, Ted Yu wrote: > > > >> > > Please use assembly:single > > > >> > > > > > >> > > See http://hbase.apache.org/book.html#maven.release > > > >> > > > > > >> > > Cheers > > > >> > > > > > >> > > > > > >> > > On Tue, Apr 22, 2014 at 4:17 PM, Konstantin Boudnik < > cos@apache.org> > > > >> wrote: > > > >> > > > > > >> > > > Guys, > > > >> > > > > > > >> > > > can anyone point me to the right direction about the tar.gz > binary > > > >> > > > assembly in > > > >> > > > 0.98? When we were building bigtop releases out of 0.94.x we > were > > > >> expecting > > > >> > > > target/hbase*tar.gz to be present. > > > >> > > > > > > >> > > > It seems the things have changes somewhat 'cause not > > > >> assembly:assembly nor > > > >> > > > package targets create the tarballs anymore. Am I doing > something > > > >> wrong? > > > >> > > > Sorry > > > >> > > > if it has been answered elsewhere... > > > >> > > > > > > >> > > > -- > > > >> > > > Regards, > > > >> > > > Cos > > > >> > > > > > > > > > > -- > > > Best regards, > > > > > > - Andy > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > Hein > > > (via Tom White) > --001a11c123f27cd7dc04f836c523--