commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@multitask.com.au
Subject Re: Commons and Maven
Date Tue, 23 Jul 2002 16:11:24 GMT
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>
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message