Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@cocoon.apache.org
From: Jorg Heymans <jh@domek.be>
Subject: Re: How long for a full trunk build (was: ParnoidCocoonServlet)
Date: Thu, 18 May 2006 22:17:51 +0200
Lines: 28
Message-ID: <e4ikp4$36g$1@sea.gmane.org>
References: <f767f0600605180638o25f6f04fg2b353234b002b619@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308)
In-Reply-To: <f767f0600605180638o25f6f04fg2b353234b002b619@mail.gmail.com>
Sender: news <news@sea.gmane.org>


Bertrand Delacretaz wrote:

> Just curious, how much time do you need for a clean build of the
> trunk, starting with an empty m2 repository?
>

I guess the maven build experience varies from country to country. For
me, with mirrors.dotsrc.org set as primary mirror and ~/.m2/repository
fully empty i can repeatedly build cocoon trunk with all blocks in about
15 minutes (20mbit connection) - uninterrupted.

> I've had several occurences where the whole thing was not finished
> after more than an hour, using an usually fast DSL or similar
> connection. For some reason, the repository downloads seem to be very
> slow here.

As Sylvain explained, there are some problems with codehaus and the main
maven repo [1], so now was probably the worst time ever to start testing
the maven build intensively. It does point out a flaw with the whole
maven architecture though, if central or a main snapshot mirror goes
down then a lot of builds will just fail, even if they have everything
local already.

Regards
Jorg

[1] http://www.codehaus.org/status.html