ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Riedel Thomas \(KSFD 121\)" <>
Subject RE: using multiple properties in the 'if' and 'unless' conditions
Date Fri, 23 Jun 2006 11:47:54 GMT
Yes I agree the kind of our Ant-usage might be a bit beyond horizon. We
are doing continious integration for a 5 Mio LOC project, generic
automated junit testing, automatic deploying into a production like
server pool, online testing, web-testing, automated metrics generation
for the architecture group, automated baseline quality level assertion,
messaging, etc.etc and all this with ant, quite error prove ;) The main
problem is that not every error or event might break the build - instead
we have different level of build quality. So the flow of the different
steps (targets) is very dynamic. We are in copious use of <if>,
<trycatch> and all the other nice contrib tasks that make ant more a
script language than an descriptive build tool. 

The other possiblity for a bit more dynamic flow of control would be a
dynamic condition, I guess. In the sense that the evaluation of the
condition should not be done once when the task is executed but every
time somebody references that condition. But thats just a guess.

-----Original Message-----
From: Steve Loughran [] 
Sent: Friday, June 23, 2006 1:08 PM
To: Ant Developers List
Subject: Re: using multiple properties in the 'if' and 'unless'

Riedel Thomas (KSFD 121) wrote:
> We have written a large library of own very sophisticated ant tasks
> all the high level stuff. What I am thinking is that especially for
> work-flow control it would be great to steer the flow between
> targets via complex if-statements. I see the point that Ant should be
> easy and descriptive, but a (somehow implemented) flow control would
> make life easier (for the integration team ;))

hey, we're trying to be a build tool, not a generic workflow system.

What is your project trying to do?

And are you using ant-contrib's <if> and <try><catch> tasks?

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

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

View raw message