Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ammulder@gmail.com designates
 64.233.184.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=BmXVgE7PinEQzeMTwznq8IMI0y6xIIZqzvkRvATqkl7BvpDCE6L88Beans5nKFZfGjLbT0xhF5ca7PGzreqCs8VsgkqJSy/7NZpTq+1bgYksdDHZvE0xNnaQgHlQYbwKDy/TszEdZRZAgD/ocin3OfzCG5FLM4rfBcbbu97ysyw=
Message-ID: <74e15baa0606070714r58f20f6ej20051cd6f11d3693@mail.gmail.com>
Date: Wed, 7 Jun 2006 10:14:57 -0400
From: "Aaron Mulder" <ammulder@alumni.princeton.edu>
Sender: ammulder@gmail.com
To: dev@geronimo.apache.org
Subject: Re: Maven Repo Woes - Temporary resolution in place
In-Reply-To: <4485F022.5020803@hogstrom.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4485F022.5020803@hogstrom.org>

This sounds good as far as it goes.  But we still have 5 single points
of failure in our build.  I would rather set up a site or zone to host
everything Geronimo needs, point all our builds to that only, and have
it create nightly packages of all the dependencies in the Maven repo
so a first-time user can download everything in one shot.

It will also help to get off Maven 1, but I think the steps above are
needed to avoid driving first-time developers away.

Thanks,
    Aaron

On 6/6/06, Matt Hogstrom <matt@hogstrom.org> wrote:
> All,
>
> I spent a couple of hours working with the Infra structure team on the build problems we've been
> experiencing.  They were really helpful in isolating the problem and effecting a solution.  Joes2
> (IRC handle on #asfinfra) was the main contact point.
>
> The problem is that people.apache.org has a limit of 10 concurrent connections on it.  The
> expectation was that Maven would only be using a single connection but that appears to not be the
> case.  The Infrastructure team has temporarily lifted the restriction while the Maven team looks
> into the issue.
>
> For our part I tested a full build with a clean repo and it only failed once (and that was an
> ibiblio problem).  At this point I think we should have smoother sailing.
>
> Next time you see an Infra guy/gal buy them a beer or two.  They're awesome to work with.  From the
> time we started talking to the time it was resolved was a little under two hours.
>
> Cheers,
>
> Matt
>