ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Rees <>
Subject Re: <available> problem
Date Tue, 20 Mar 2001 19:58:00 GMT
On 20 Mar 2001 08:31:45 +0100, Stefan Bodewig wrote:

>Vincent Massol <> wrote:
>> I was more concerned about the <available> task. It shouldn't define
>> the property if the file cannot be found, right?
>but it doesn't 8-)
>file="" means "" relative to the project's basedir, which in turn
>means the basedir itself - which exists.  If you really need something
>that fails, "" is the worst of all choices.
>To Nico and Steve, I think the current behavior is correct and that we
>shouldn't have different behavior for files and directories.  There
>might even be some build files out there that use file="some-dir" and
>expect it to set the property if that directory exists.

Is there a way to unset a property? I have not come across this (and
would really like to)? If am thinking he could use this to be the
condition (since its not really the file but the fact that a string is
blank that he cares about).

View raw message