Oh, right, yeah; that'd work. I just didn't go far enough with my original decomposition! :=)
Thanks, L. On Mon, 2001-11-19 at 03:26, Nico Seessle wrote: > ----- Original Message ----- > From: "Laurie Harper" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: "'Ant Users List'" <[EMAIL PROTECTED]> > Sent: Monday, November 19, 2001 7:51 AM > Subject: RE: Requiring multiple properties to be set > > > > No, unfortunately; I have a single task that requires all three > > properties to be set. It can't be broken into three seperate tasks > > because the properties supply command line arguments to an external > > script. > > > > And what about > > <target name="test1" unless="p1"> > <fail message="Property p1 must be defined"/> > </target> > <target name="test2" unless="p2"/> > <fail message="Property p2 must be defined"/> > </target> > <target name="test3" unless="p3"/> > <fail message="Property p3 must be defined"/> > </target> > <target name="mainTarget" depends="test1, test2, test3"/> > > Nico > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- zodiac(@)holoweb!net | "If that's too much initiative for the company to ICQ# 78724820 | handle, I don't want to work for them anyway." -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
