Return-Path: Delivered-To: apmail-community-archive@apache.org Received: (qmail 44461 invoked by uid 500); 27 Feb 2003 17:46:45 -0000 Mailing-List: contact community-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: community@apache.org Delivered-To: mailing list community@apache.org Received: (qmail 44448 invoked from network); 27 Feb 2003 17:46:45 -0000 Received: from web12403.mail.yahoo.com (216.136.173.130) by daedalus.apache.org with SMTP; 27 Feb 2003 17:46:45 -0000 Message-ID: <20030227174649.43381.qmail@web12403.mail.yahoo.com> Received: from [216.146.93.6] by web12403.mail.yahoo.com via HTTP; Thu, 27 Feb 2003 09:46:49 PST Date: Thu, 27 Feb 2003 09:46:49 -0800 (PST) From: Morgan Delagrange Reply-To: morgand@apache.org Subject: RE: [proposal] daedalus jar repository (was: primary distribution location) To: community@apache.org, dion@multitask.com.au In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --- Costin Manolache wrote: > On Fri, 28 Feb 2003 dion@multitask.com.au wrote: > > > .... > > > In other words - as long as maven decisions > affect only maven - I don't > > > care. But if it affects other projects, and the > repository certainly does > > > - then the PMCs of those projects or the apache > community are the ones > > > that decide. > > Sure, but please take into account the work we've > already done. > > Of course. The "maven" word comes up quite > frequently on this thread :-) > The issue is that the repository on daedalus will > affect all apache > projects that choose to use it ( to download and > upload files ). > Certainly a daedalus repository could be of use to many projects. One feature I would LOVE to see is a repository that contained the HEAD versions of every JAR in addition to snapshots, releases, etc. If I could flip a switch in my Maven, Ant, Centipede, etc. script and compile my project against the absolute latest and greatest, that would be an extremely useful sanity check. Whether those HEAD jars are built by Maven, GUMP, Centipede or "Tool X" makes no difference to me. However since GUMP is one of the only tools (perhaps the only tool?) that currently does the job, I find the statement that GUMP "sucks" disingenuous. Is GUMP easy to deploy for your own environment? Not really. Is it useful for building individualy projects a la Maven? No. Does it provide an effective continuous integration environment for Apache? Yes indeed. Does it suck? Hardly. If parts of GUMP are awkward, it's only because continuous integration is a thankless job. Thanks, GUMP. :) - Morgan ===== Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: community-unsubscribe@apache.org For additional commands, e-mail: community-help@apache.org