ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: TimeStamp dependent target execution
Date Fri, 07 Jul 2000 13:13:25 GMT

Point taken from both Stefan and Marius.  I guess I'm just a little gun shy
lately.  I've been using the old April release of Ant for too long now, and
it didn't have all the flexibility that the current CVS release has.  I
went through some serious hoops to get our very modular build working by
creating extensions to the available task and creating new ifdef and ifndef
tasks.  It makes for a very flexible but difficult to understand build
file.  With the latest release, I can reduce a lot of that complexity (if
they ever give me the time... :-).

At any rate, I like the idea of a transform task, but doesn't that bring up
a number of issues that got hashed out about a month ago about making Exec
a MatchingTask?  I don't remember all the details, but I do remember a
rather lively discussion. :-)

Glenn McAllister
TID - Software Developer - VisualAge for Java
IBM Toronto Lab, (416) 448-3805
"An approximate answer to the right question is better than the
right answer to the wrong question." - John W. Tukey

Please respond to

Subject:        Re: TimeStamp dependent target execution

>>>>> "GM" == glennm  <> writes:

 GM> The feel I've gotten over the past couple of months is that many
GM> of the main developers on this project don't want Ant to become
GM> another programing language

Trust your feelings 8^).

What Marius suggests is something different though. He proposes
another available like task that just sets a property and builds upon
the already introduced infrastructure of target-if and
MatchingTask.NameEntry-if and -unless.

I have another idea to solve the same problem - see other post. Other
than that, I don't see why something like obsolete should be
considered more evil than available.

They've been invented for different purposes of course - available is
there to allow highly modular projects to be built from a single
buildfile, while obsolete is there to move responsibility outside of
tasks. But I've already seen available being "abused" for similar
things (create a file if something has changed, use available to check
whether the file is there and only run the target when it is).


View raw message