Return-Path: 
 <dev-return-48274-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 13373 invoked from network); 28 Sep 2003 18:04:27 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 28 Sep 2003 18:04:27 -0000
Received: (qmail 97369 invoked by uid 500); 28 Sep 2003 18:04:14 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 97336 invoked by uid 500); 28 Sep 2003 18:04:13 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 97319 invoked from network); 28 Sep 2003 18:04:10 -0000
Received: from unknown (HELO lapgp.otego.com) (62.167.79.1)
  by daedalus.apache.org with SMTP; 28 Sep 2003 18:04:10 -0000
Received: (qmail 23927 invoked from network); 28 Sep 2003 18:04:06 -0000
Received: from localhost.pati.ch (HELO localhost) (127.0.0.1)
  by localhost.pati.ch with SMTP; 28 Sep 2003 18:04:06 -0000
Date: Sun, 28 Sep 2003 20:04:05 +0200 (CEST)
From: Giacomo Pati <giacomo@apache.org>
Sender: giacomo@lapgp.otego.com
To: Cocoon Development <dev@cocoon.apache.org>
Subject: [Vote] Build infrastructure (was: on better release and version
 management)
In-Reply-To: <2A3CDA39-EF43-11D7-AD24-000393D2CB02@apache.org>
Message-ID: <Pine.LNX.4.53.0309281944260.25463@lapgp.otego.com>
References: <2A3CDA39-EF43-11D7-AD24-000393D2CB02@apache.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Thu, 25 Sep 2003, Stefano Mazzocchi wrote:
> On Thursday, Sep 25, 2003, at 10:47 Europe/Rome, Giacomo Pati wrote:
>
> > On Wed, 24 Sep 2003, Berin Loritsch wrote:

<snipped>discussion on build infrastructure</snipped>

> >>
> >> We tried to have a unified build system with ANT, and all excalibur
> >> projects
> >> re-using part of the central build file, etc.  NIGHTMARE CITY.
> >>
> >> Contrast that with the parts that were ported over to use Maven, or
> >> the GUIApp
> >> project (http://d-haven.org).  A world of difference.  No longer is
> >> there any
> >> question about what is needed where.  No longer is there a need to
> >> have JARs
> >> locally in the repository.  No longer is there a need to have a 13 MB
> >> download
> >> for a full distributable.  Not to mention, it makes it easier to find
> >> out what
> >> exactly is a dependency and what is dead weight.
> >
> > seconded!
>
> are you (or Berin) volunteering? [again, not caustic, just curious]

Well, as my time permits it and Berin could give a hand as well, why
not.

But first we need to come to a consensus about which build
infrastructure we would support to use:

1) Ant
     in this case we can use the current build system and tune it to the
     needs we have for the 2.2 and maybe add some ruper task to get rid
     of jars in our repository (suggested by Nicola Ken IIRC) and some
     more for modularisation ease

2) Centipede
     in this case I could not volunteer as I'm out of Centipede since
     their move from Cents to Antlibs (we still have some customer
     project using a Cents based version of it but they will never move
     to Antlibs)

3) Maven
     ATM this is my preferred build infrastructure and I could help
     building the 2.2 repo based on it

Please show your preferences (if you don't have a clue about Maven
and/or Centipede have a look at their sites at http://maven.apache.org
and http://www.krysalis.org/centipede/ respectively)

--
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com