commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Keyes <j...@mac.com>
Subject Re: unmavenising Commons projects
Date Mon, 24 Jun 2002 15:28:18 GMT
> But again, why talk about this? If Costin wants them moved, then away he 
> goes. Or gets the committer of the changes to roll them back. It's not 
> like it's an all or nothing scenario here. The two can quite peacefully 
> coexist.
The reason I posted that was to highlight that Maven builds 
and ant builds can coexist peacefully.  It seemed that this 
was being lost in the whole process discussion.

-John K

> --
> dIon Gillard, Multitask Consulting
> Work:      http://www.multitask.com.au
> Developers: http://adslgateway.multitask.com.au/developers
> 
> John Keyes <jbjk@mac.com> wrote on 06/24/2002 07:44:26 PM:
> 
> > Folks the discussion here should not be about what GUMP is or
> > what Maven is.  It should be about standardizing the build 
> > process for Commons. 
> > 
> > It seems that the general consensus is that to satisfy all 
> > parties there should be two ant projects, build.xml and
> > build-maven.xml.  Could this issue be resolved with just one 
> > project, build.xml.
> > 
> > The default target for this project must generate the binary
> > distribution.  If the default target is 'dist' then both scenarios
> > could be accomodated as follows:
> > 
> > <target name="dist" depends="ant-dist, maven-dist"/>
> > 
> > <target name="ant-dist" unless="maven.home">
> >   ...
> > </target>
> > 
> > <target name="maven-dist" if="maven.home">
> >   ...
> > </target>
> > 
> > Just an idea,
> > -John K
> > 
> > On Mon, 2002-06-24 at 08:24, Henri Yandell wrote:
> > > 
> > > > > Just don't try to present ant as 'legacy' and replace the 
> build.xml
> > > > > and the conventions we use with something else.
> > > > Who is? Where has someone declared ant as 'legacy'? And please tell 
> me
> > > > about the consistent conventions used across commons....
> > > 
> > > My fault. I've been referring to the build.xml's that were replaced as
> > > legacy build.xml's that should be kept until we maven is at a point 
> where
> > > we can consider standardising on it.
> > > 
> > > Hen
> > > 
> > > 
> > > --
> > > To unsubscribe, e-mail: 
> <mailto:commons-dev-unsubscribe@jakarta.apache.org
> > >
> > > For additional commands, e-mail: 
> <mailto:commons-dev-help@jakarta.apache.org
> > >
> > > 
> > 
> > 
> > 
> > --
> > To unsubscribe, e-mail: 
> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail: 
> <mailto:commons-dev-help@jakarta.apache.org>
> > 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> 



--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message