Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates
 209.85.192.51 as permitted sender)
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: 
 <CA+RK=_BnRHM=EpDFffZG8pdd850zy0_X+77bYggYzB7h3EEqyw@mail.gmail.com>
References: <20140422231718.GP22142@boudnik.org>
	<CALte62zBzhvM2K3Et273WOxxX=KnQn-npFy89NSrtEMERJksaQ@mail.gmail.com>
	<20140423022649.GS22142@boudnik.org>
	<20140429213832.GY6333@boudnik.org>
	<CA+RK=_ACmYEygzg6s+cNymT4HmRyOtrkmr+8Ffodwk3frD_rag@mail.gmail.com>
	<CA+RK=_CYrUGn5md3Lu5xBsL8JpchvDJD_6Sgvf=6a5tynj0-gw@mail.gmail.com>
	<20140429215422.GZ6333@boudnik.org>
	<20140429231851.GC6333@boudnik.org>
	<CADcMMgEKdhHiqvMnx7VbZtQ9mWr9e1djFf0Q=vjmyjmQi6c-=w@mail.gmail.com>
	<20140429233754.GD6333@boudnik.org>
	<CA+RK=_BnRHM=EpDFffZG8pdd850zy0_X+77bYggYzB7h3EEqyw@mail.gmail.com>
Date: Tue, 29 Apr 2014 22:35:19 -0700
Message-ID: 
 <CADcMMgFcwpFtW1Sy921fvHeQpLMuuMrA2K_5tujzpUNib1Hzcg@mail.gmail.com>
Subject: Re: 0.98.1 has stopped building [Was: What happened to tar.gz
 assembly in 0.98?]
From: Stack <stack@duboce.net>
To: HBase Dev List <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2b994fd524904f83be9a2

--001a11c2b994fd524904f83be9a2
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 29, 2014 at 6:45 PM, Andrew Purtell <apurtell@apache.org> wrote:

> We have a 'release' Maven profile. Right now it just runs Apache RAT. I
> wonder if some kind of hairy Maven-foo can reattach site into the right
> place if this profile is enabled. RAT is pretty quick, and Javadoc is going
> to dominate build time anyhow, so should be ok for Bigtop packaging. The
> question is if it's possible. My Maven is weak. Anyone have any idea?
>
>
>
Seems like site is a lifecycle of its own apart from the maven 'default'
lifecycle:
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
Getting the site lifecycle to run inside a goal of the 'default'
lifecycle
could be tough (I'm no expert).  We make use of the pre-site building
docbook.
St.Ack


> On Tue, Apr 29, 2014 at 4:37 PM, Konstantin Boudnik <cos@apache.org>
> wrote:
>
> > On Tue, Apr 29, 2014 at 04:27PM, Stack wrote:
> > > On Tue, Apr 29, 2014 at 4:18 PM, Konstantin Boudnik <cos@apache.org>
> > 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.
> >
> > Yeah, you right. it also won't fly for another reason - the install won't
> > engage other needed steps such as compile, test-compile, etc. It seems
> that
> > for the purpose of Bigtop packaging there's no other way but to really
> > execute
> > two septate mvn process one after another.
> >
> > Thanks,
> >   Cos
> >
> > > 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 <
> > apurtell@apache.org>
> > > > 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 <
> > cos@apache.org
> > > > >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)
> > > >
> >
>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

--001a11c2b994fd524904f83be9a2--