ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stirling, Scott" <>
Subject RE: uptodate vs. outofdate and if/unless gotchas
Date Thu, 04 Mar 2004 18:24:22 GMT
> From: Peter Reilly []
> The name of outofdate was a play on uptodate to show that
> it does the opposite.

Ahh.  Interesting.
> As Dominique says, its main purpose is to run an embedded list
> of tasks if the outofdate condition is set.

That makes little sense to me from a design perspective, although it's a nice feature and
I won't complain.  I mean, running an embedded list of tasks based on a condition is great.
 Why narrow it only to the condition of whether files are outofdate?  Missed opportunity for
abstraction for all the other conditions why you might want to run a task, right?

> I have never liked the ant idiom of using properties to control
> program execution logic.

Doesn't bother me a bit because I find it useful in a variety of scenarios (i.e., stuff supported
by available/condition/if tasks).  I used to hate using flow control tasks from antcontrib
in Ant scripts, but I've loosened up on it since it lets you do mo' better stuff in Ant without
shelling out or writing a custom task.

Scott Stirling
Workscape, Inc.

This message is intended only for the use of the intended recipient and
may contain information that is PRIVILEGED and/or CONFIDENTIAL.  If you
are not the intended recipient, you are hereby notified that any use,
dissemination, disclosure or copying of this communication is strictly
prohibited.  If you have received this communication in error, please
destroy all copies of this message and its attachments and notify us

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

View raw message