DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33074>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33074 Summary: condition task should support optional value for false Product: Ant Version: 1.6.2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P4 Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] It would be convenient to have the condition task take an additional "otherwise" value for the property if the condition evaluates to false. Not supplying this woulg give the current behaviour, i.e. not setting the property. The workaround is simple enough: use the condition task to set if true, and a subsequent property task to set if it hasn't been set yet (condition was false.) It would be both more elegant and clear with something like <condition property="prop1" value="true" otherwise="false"> <some supported condition> </condition> The code change is simple. The documentation changes are a little more substantial. (I tested the former, but haven't investigated the latter.) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
