This is what JUnit is for! :)
Write some test cases to ensure that your tasks are behaving as expected.
Ant's codebase has infrastructure I encourage you to investigate and perhaps
borrow for your own custom tasks.
You could workaround by having some conditional targets that depended on
targets that output key properties, and just run once without setting the
property, and then again after you've verified things are set as you desire
with the conditional property set.
Erik
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 25, 2002 9:58 AM
Subject: Re: Dumb question: equivalent of make -n?
> On 25 Jan, Erik Hatcher wrote:
> > No, Ant has no such option. This would be difficult given Ant's
> > differences with make - make handles the dependency checking itself,
> > whereas Ant's tasks handle it.
> >
> > What exactly do you want to "verify" about a new task?
> >
>
> That I've written it correctly and that the operations that will take
place
> are really those I expect. It's more to verify that I'm correct rather
than
> that ant is correct. This is more important to me when I'm writing a
> destructive task (a task that can change data in a database, that deletes
or
> renames files, stuff like that).
>
> For example, I've had at least one instance where my .ant.properties file
> contained the incorrect schema for a test I was doing and I modified the
> wrond data. It wasn't a critical error but it coulda been.
>
> L
>
> --
> Laurent Duperval <mailto:[EMAIL PROTECTED]>
>
> "I realized that the purpose of writing is to inflate ideas, obscure poor
> reasoning, and inhibit clarity."
> -Calvin
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
