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] - condition fails to set property that has previously been set
Date Tue, 15 Oct 2002 09:30:48 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

condition fails to set property that has previously been set





------- Additional Comments From jakarta@ehatchersolutions.com  2002-10-15 09:30 -------
It was a "bug" that it worked in previous versions and it only worked in certain
tricky ways.  There are very good reasons why property immutability is a Good Thing.

You might want to reconsider how you're implementing  your build file.  There
are ways around this by using <antcall> (which is an isolated new Ant "stack"
that can have its own properties without affecting the calling Ant).

--
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