ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 13632] - should error when condition attempts to set property that has previously been set
Date Tue, 15 Oct 2002 18:38:30 GMT
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=13632>.
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=13632

should error when condition attempts to set property that has previously been set





------- Additional Comments From jakarta@ehatchersolutions.com  2002-10-15 18:38 -------
Again, this is by design to *not* error.  What if, and this is not a
hypothetical "what if", you wanted to force the setting of a property from the
outside on occasion but by default it used a condition.  Having it error is not
the desired behavior.  Ant's very own build file takes advantage of this type of
thing even.

I'll leave this open this time with the idea that a change could be made to add
a 'failonexistence' property (or some nicer name) that you could set to true and
force a failure in this case, but it would be something you'd have to specify
for each <condition> manually.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message