ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From STEELE Edwin <>
Subject Unsetting properties
Date Wed, 05 Jun 2002 01:07:38 GMT
	The if and unless attributes on tasks only check
whether the a property has been set or not. It doesn't
look like a task can have multiple properties to check
in an if or unless attribute (unlike the depend attribute)
so I'm wondering whether there is any reason why an
unsetProperty type task couldn't be implemented.

Is there an assumption that once a property is set, it
will remain set?


This e-mail and any attachment to it is intended only to be read or used by
the named addressee.  It is confidential and may contain legally privileged
information.  No confidentiality or privilege is waived or lost by any
mistaken transmission to you.  If you receive this e-mail in error, please
immediately delete it from your system and notify the sender.  You must not
disclose, copy or use any part of this e-mail if you are not the intended
recipient.  The RTA is not responsible for any unauthorised alterations to
this e-mail or attachment to it.  

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

View raw message