Return-Path: 
 <commons-dev-return-12227-qmlist-jakarta-archive-commons-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@apache.org
Received: (qmail 55109 invoked from network); 23 Jul 2002 15:56:31 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 23 Jul 2002 15:56:31 -0000
Received: (qmail 3974 invoked by uid 97); 23 Jul 2002 15:56:48 -0000
Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org
Received: (qmail 3876 invoked by uid 97); 23 Jul 2002 15:56:48 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 3807 invoked by uid 98); 23 Jul 2002 15:56:47 -0000
X-Antivirus: nagoya (v4198 created Apr 24 2002)
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: Commons and Maven
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V60_M13_04302002 Pre-release 2 April 30, 2002
From: dion@multitask.com.au
Message-ID: 
 <OFC4C07C34.0B3585EA-ON4A256C01.0040DCAF-4A256C01.00418AAF@multitask.com.au>
Date: Wed, 24 Jul 2002 02:11:24 +1000
X-MIMETrack: Serialize by Router on gateway/Multitask Consulting/AU(Release
 5.0.8 |June
 18, 2001) at 07/24/2002 02:11:29 AM,
	Serialize complete at 07/24/2002 02:11:29 AM
Content-Type: multipart/alternative;
 boundary="=_alternative 0040E80A4A256C01_="
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

--=_alternative 0040E80A4A256C01_=
Content-Type: text/plain; charset="US-ASCII"

Will there be a b5 release of Maven before this happens? I'd hate for 
people to have to go bootstrap maven themselves just to test it out.
--
dIon Gillard, Multitask Consulting
Work:      http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers


Jason van Zyl <jason@zenplex.com> wrote on 07/23/2002 11:47:38 PM:

> Hi,
> 
> I just finished making a first pass at a master project.xml descriptor
> for the commons along with subclass project.xml files for most of the
> commons projects. With this mechanism there is a parent project.xml file
> in the top-level commons directory and each project has something that
> looks like this:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> 
> <project>
>   <extend>../project.xml</extend>
>   <name>commons-beanutils</name>
>   <id>commons-beanutils</id>
>   <currentVersion>1.0-dev</currentVersion>
>   <inceptionYear>2000</inceptionYear>
>   <shortDescription>Commons Bean Utils</shortDescription>
>   <description>Java Bean Utililities</description>
> 
>   <developers>
>     <developer>
>       <name>Craig McClanahan</name>
>       <id></id>
>       <email></email>
>       <organization></organization>
>     </developer>
>   </developers>
> 
>   <dependencies>
>     <dependency>
>       <id>commons-logging</id>
>       <version>1.0</version>
>     </dependency>
>     <dependency>
>       <id>commons-collections</id>
>       <version>2.0</version>
>     </dependency>
>     <dependency>
>       <id>junit</id>
>       <version>3.7</version>
>     </dependency>
>   </dependencies>
> 
>   <build>
>     <unitTest>
>       <includes>
>         <include>**/*TestCase.java</include>
>       </includes>
>     </unitTest>
>   </build>
> 
> </project>
> 
> Almost all the pertinent project information is gleaned from the parent
> template using a combination of inheritance and interpolation. The
> parent looks like this:
> 
> http://www.apache.org/~jvanzyl/project.xml
> 
> The ant/gump generation is working pretty well now, I have set up a
> small reactor-like build in the top-level of the commons to build all
> the projects and generate all the sites. And we are working on a
> scheduler tag for Jelly and we are going to integrate Werkflow
> (http://werkflow.werken.com) so we can do some cool continuous
> integration work.
> 
> At any rate all maven needs is the project.xml files (in some cases a
> maven.xml for pre/postGoals) and I think this will help really make the
> projects in the commons common :-) While trying to build the projects
> with the reactor I can see tons of little things that are slightly
> different that would throw new users off. Nothing serious, but I think
> this is an opportunity to unify and I believe Maven is at the point
> where it would more of a boon and less of an irritation.
> 
> I would like to check in a master project.xml file and all the subclass
> builds. Maven doesn't have to generate an ant build or a gump descriptor
> so if a particular commons project wants to keep their hand-crafted
> build.xml file and gump descriptor then that works perfectly well.
> 
> I am an enthusiastic and excited
> 
> +1
> 
> -- 
> jvz.
> 
> Jason van Zyl
> jason@apache.org
> http://tambora.zenplex.org
> 
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
> 
>   -- Jacques Ellul, The Technological Society
> 
> 
> --
> To unsubscribe, e-mail: 
<mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
<mailto:commons-dev-help@jakarta.apache.org>
> 

--=_alternative 0040E80A4A256C01_=--