ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject RE: "if" task
Date Tue, 30 Apr 2002 23:35:29 GMT
I'm a bit scared to weigh into this debate/holy war, but here goes :)

What about treating contrib like optional? Include it as a separate download
but still under the main umbrella?

Personally, I found it difficult without <if> at first, but once I figured
it out its now just fine and I rarely have to use the "if, unless" feature
of a task. Its all about getting the structure of your build right and this
is probably the very reason <if> is left out - too easy to write lazy,
poorly structured builds with it :)

Anyone who really wants it should be made to download it separately (or
write it themselves... surely it can be done in about 5 lines of code
exluding class & function definitions?!)

Anyway, my A$0.04 (Needed to up it to get the $0.02 USD - darn exchange rate


-----Original Message-----
From: Martin Jericho []
Sent: Wednesday, 1 May 2002 9:29 AM
Subject: "if" task

I have a very pragmatic solution to this problem.  Include a reference to
the contrib stuff in both the resources and FAQ sections of the ANT
documentation.  Someone has already mentioned that it is in the FAQ of the
website, but I didn't check that because I had already checked the FAQ that
came with the download.  If it is put in a prominent place where newbies can
easily find it, it will no doubt save them a lot of time, and would have
saved me a lot of time.

Now I have a question for you Steve:
You said you don't have much need for conditionality apart from <fail>.
This is exactly what I want to use it for, but there is no conditionality
built into fail either.  So how do you do it?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message