Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <40A4234B.6050607@latte.harvard.edu>
References: <40A3434A.40708@apache.org>
 <002401c4391f$b92fbf20$604a9951@oemcomputer>
 <7B406D7D-A51C-11D8-89E3-000393DB559A@coredevelopers.net>
 <003301c4393a$91cf8800$fc059a51@oemcomputer>
 <40A4234B.6050607@latte.harvard.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <FAA0F870-A5D7-11D8-89E3-000393DB559A@coredevelopers.net>
Content-Transfer-Encoding: 7bit
From: Dain Sundstrom <dain@coredevelopers.net>
Subject: Re: [collections] new snapshot to ibiblio
Date: Fri, 14 May 2004 13:53:24 -0500
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>

On May 13, 2004, at 8:39 PM, Mark R. Diggory wrote:

> There is a convergence between the Gump Integration and this unstable 
> repository which I hope is occurring, eventually, we hope that Gump 
> will be used to produce a nightly build repository for projects, and 
> that most projects will start taking advantage of this Continuous 
> Integration for their development. I have been watching (lurking?) the 
> Gump folks diligently working on this and I think its coming along.

I think that implying that Gump will be used by every project is a bit 
ivory tower.  The reality is some projects simply don't want or need 
continuous integration.  Also, Gump is not the only continuous 
integration system in opensource.  I am very concerned that about 
linking access to SNAPSHOTs to the use of a continuous integration 
system.

> Until this is complete, the unstable repository is available for those 
> who need to release unstable builds. Because it is on cvs.apache.org, 
> it is not mirrored, nor does it endup at ibiblio. This unstable 
> repository should not be utilized by non-apache developers, 
> eventually, we may consider some form of security to restrict access 
> to it.

This is a no go for geronimo.  There are 3 other projects outside of 
apache that use geronimo snapshots and geronimo in return imports the 
snapshots from these other projects in to the final assembly.  If 
snapshot access were turned off, our entire build system would stop to 
work.

-dain


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org