Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 1987 invoked by uid 500); 20 Mar 2001 20:07:02 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 1800 invoked from network); 20 Mar 2001 20:06:29 -0000 From: David Rees To: ant-dev@jakarta.apache.org Subject: Re: problem Date: Tue, 20 Mar 2001 11:58:00 -0800 Reply-To: d.rees.l@usa.net Message-ID: References: <003d01c0b098$36f901a0$0200005a@vizzavi.fr.corp.vizzavi.net> <3AB64294.101A40CD@somanetworks.com> <00e201c0b0a4$15b06220$0200005a@vizzavi.fr.corp.vizzavi.net> In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On 20 Mar 2001 08:31:45 +0100, Stefan Bodewig wrote: >Vincent Massol wrote: > >> I was more concerned about the task. It shouldn't define >> the property if the file cannot be found, right? > >but it doesn't 8-) > >file=3D"" 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=3D"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).