ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiller, Dean D \(Dean\)" <>
Subject RE: don't copy build.xml files ever again.....
Date Tue, 14 Sep 2004 13:45:32 GMT
I actually have a hard time using import cross-project as I can't import
something that is non-existent in the other project.  :)

Also, I hear very well what scares you as that is why this is a pattern,
not a library solution per say. People are free to use, but the real
idea is you have your own template.  It works out very well in SOA
environments where you have many different modules that don't know how
to share build.xml files!!!  You could use unix/linux and link behind
CVS, but you run into trouble on different file systems.  This is a new
methodology which is working out great when you have many modules that
have similar build.xml files.

-----Original Message-----
From: Stefan Bodewig [] 
Sent: Monday, September 13, 2004 12:35 AM
Subject: Re: don't copy build.xml files ever again.....

On Sat, 11 Sep 2004, Dean Hiller <> wrote:

> Ever find yourself copying a build.xml file only to add stuff to it
> later like code coverage and wish you could add to all those other
> projects you copied the build.xml file from.

Yes.  Whenever I do, I use <import> to import that build file I'd
otherwise copy 8-)

> What is really nice, is you only have to check in,
> build.bat, buildtemplate.jar, junit.jar,, dist.xml
> each time you upgrade.

With <import> I only do this for the module that contains the build
file I import.

> ant, emma, jdk package lists, ant-contrib and a bunch of goodies are
> hidden inside the buildtemplate.jar.

This would scare me, since I don't have control over its contents any




To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message