I'm not a committer, but I'd like to throw in my (unofficial) +1 on the side of throwing a BuildException. I've routinely been bitten by having builds create strange folders and copy files into the wrong place.
This would clear up a lot of my build files that have extra targets for <fail> if environment variables (e.g. system dependent install dirs) aren't set. Tim > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 30, 2001 3:38 AM > To: [EMAIL PROTECTED] > Subject: [VOTE] how will Ant2 deal with undefined properties > > > As a side effect of the "tasks as sibblings of targets" thread, there > seemed to be agreement that ${a} should throw a BuildException if > there is no property "a" in Ant2. > > As only three committers have participated in this discussion, others > may have missed that, so I'm putting it up for a formal vote. > > If there is no property a, shall ${a} > > (1) throw a BuildException > > or > > (2) evaluate to ${a} like it does in Ant 1.x. > > Stefan > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
