ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <>
Subject Re: ANT visions and best practices
Date Thu, 27 Feb 2003 18:08:20 GMT

I would back up Simon's comments, and add that seems to have
better ship time & pricing, at least the last time I looked. In the
meantime, Ant in Anger covers some of the topics.


1. Download xdoclet from and start looking at it as the way
of generating all your EJB deployment descriptors, taglibs, etc.

2. look at junit, httpunit and cactus, if you havent already. Java tools for
Extreme Programming is another book in this area.

3. Get a copy of IntelliJ IDEA

4. Set up an automated build system, such as CruiseControl
(, for a continuous build.

5. automate all deployment, post deployment testing,

6. treat deployment config problems as defects and write tests for them
before you fix.

I have some papers and presentations you might find interesting at


----- Original Message -----
From: "Chappell, Simon P" <>
To: "Ant Users List" <>
Sent: Thursday, February 27, 2003 09:54
Subject: RE: ANT visions and best practices

That's quite an application you have there. Looks like this would benefit
from a divide and conquor approach. Start by figuring out the dependencies
between deliverables. Can you build the client without the DB and EJB's? If
you can, then keep that as a sub-project and let it have it's own build
file. We don't use EJBs here yet, so someone else will need to offer code
for building those. Build those separately and use the resulting JAR files
as dependencies for other sub-projects that need them.

Summary: build each module as a separate sub-project. Use the output from
builds as the input to other builds. Keep asking for help.

Pay for overnight shipping on the Ant book or find a bookstore that would
carry it. Sometimes you just have to bite the bullet and buy the book
yourself to get the job done in realistic timeframes (just ask my poor wife,
who shakes her head everytime a parcel arrives from at our


View raw message