You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ant.apache.org by bu...@apache.org on 2003/05/21 02:26:36 UTC

DO NOT REPLY [Bug 20085] - If a propert is unset, property substitution does nothing

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20085>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20085

If a propert is unset, property substitution does nothing

conor@cortexebusiness.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From conor@cortexebusiness.com.au  2003-05-21 00:26 -------
Workaround is to set the property after the env load

<property name="env.ALERT_DIR" value=""/>

If it has a value, this has no affect, otherwise it will be set to an empty string. 

Is it a bug? Maybe, but it is the way it is and changing it may be difficult
since some people may rely on it to catch errors. Think about

<delete dir="/${location}"/>

:-)

Ant 1.6 will probably allow you to plug in a different Property resolution
system which could react differently such as to throw an exception (my
preference) or to use an empty string, etc.