ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Testing Optional Ant Tasks
Date Mon, 05 Aug 2002 20:50:48 GMT

That would be useful.

I have looked at the AbstractCvsTaskTest class and made some sense of how
things are being tested.  It looks a lot like I expected.
My biggest problem is knowing all the clever little utilities that exist.
(i.e. getProject().resolveFile("tmpdir/jakarta-ant/build.xml"))
I get the impression the Project class exposes most of these.

James Lee Carpenter
Software Engineer
Household Technical Services
6602 Convoy Court
San Diego, CA 92111

ph: 858-609-2461

                        "Steve Loughran"       To:    "Ant Developers List" <>
                        <steve_l@iseran.c      cc:                                    
                        om>                    Subject:    Re: Testing Optional Ant Tasks
                        08/05/2002 01:34                                                 
                        Please respond to                                                
                        "Ant Developers                                                  

----- Original Message -----
From: "Erik Hatcher" <>
To: "Ant Developers List" <>
Sent: Monday, August 05, 2002 13:09
Subject: Re: Testing Optional Ant Tasks

> Have a look in Ant's CVS tree.  There is a base class, exactly as you
> suspected.  As for being documented - not really, but once you browse
> Ant's source tree in the test cases area you'll get the hang of it
> relatively easily.
> And we're here to help if you run into more questions along the way.
> Erik

there is the intent to make the test class a standalone jar for easier of
testing of 3rd party tasks; someone needs to sit down and edit build.xml to
create this.

Also, while there *isnt* anything on testing ant tasks in the
soon-to-be-seminal Java Development with Ant book, there are 5+ pages on
subject in its CVS repository that Erik or I could retrieve, update to the
latest version of the test classes (it was written against the old one),
then add to the ant documentation. Same for another out-take: common build
file problems and how to diagnose them.


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

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

View raw message