Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 46082 invoked from network); 29 Sep 2003 13:12:36 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 29 Sep 2003 13:12:36 -0000 Received: (qmail 34997 invoked by uid 500); 29 Sep 2003 13:12:24 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 34970 invoked by uid 500); 29 Sep 2003 13:12:24 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 34921 invoked from network); 29 Sep 2003 13:12:24 -0000 Received: from unknown (HELO onramp.i95.net) (205.177.132.17) by daedalus.apache.org with SMTP; 29 Sep 2003 13:12:24 -0000 Received: from apache.org ([66.208.12.130]) by onramp.i95.net (8.12.10/8.12.9) with ESMTP id h8TDCOk6007450 for ; Mon, 29 Sep 2003 09:12:24 -0400 Message-ID: <3F782FB9.9060805@apache.org> Date: Mon, 29 Sep 2003 09:12:25 -0400 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [Vote] Build infrastructure References: <2A3CDA39-EF43-11D7-AD24-000393D2CB02@apache.org> <33152.10.0.0.5.1064776610.squirrel@ags01.agsoftware.dnsalias.com> <33202.10.0.0.5.1064781929.squirrel@ags01.agsoftware.dnsalias.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Nicola Ken Barozzi wrote: > Antonio Gallardo wrote: > ... > >> I think it is better to save our efforts by using any of the projects >> related to this tasks. The idea, is to have a better project management >> with less effort than we currently have with Ant. Is that right? > > > Correct. > > I strongly think that moving to Maven now will be a major and > unnecessary disruption in our development process, and I don't want to > see it. > > As I said, it's quite easy to have almost all that Maven provides by > using other stuff. > > What do we want from Maven? > > 1 - jar downloads: use Ruper or Ant > 2 - generic targets? Heck, we already have them. > 3 - what else? Don't tell me activity reports, because it's an > Ant task that Maven simply uses. > > Let's not go into a massive build-system change that will make it even > harder to sense what's happening, and lay out what we need. > > NOTE: I'm the original Centipede author, so yes, I'm definately baised > Once it is set up it works. It can be set up in parallel to the existing build system--so impact for the migration only really happens after all the bugs have been worked out. I am not an author for either Centipede or Maven, just someone who has used Maven and had it satisfy my needs. -- "They that give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin