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 10386] - condition with isset does not return valid results on ${env.<varname>} when varname is not defined
Date Wed, 03 Jul 2002 23:39:18 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=10386>.
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=10386

condition with isset does not return valid results on ${env.<varname>} when varname
is not defined





------- Additional Comments From vpatryshev@borland.com  2002-07-03 23:39 -------
It is obvious that when var0 is not set, the condition with isset does not set
the variable. But another condition, <not> <isset> does not set the variable either.

Yes, I agree; I can actually do something like this:

<property name="value_of_var0" value="not_assigned"/>
<condition property="value_of_var0" value="${env.var0}">
  <isset property="env.var0"/>
</condition>

Meaning that yes, I can bypass it.

But it is still a bug. Logical operators should work in a logical way.

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