mmm, I have recently felt the need for conditional filesets; I had to hack something with conditional patternsets instead.
----- Original Message ----- From: "Jose Alberto Fernandez" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, November 26, 2002 2:58 AM Subject: RE: [PATCH] adds 'if'/'unless' to <antcall> (CallTarget.java) If people really need to do contitional things they should just use the <if/> task that comes as part of ant-contrib. The if/unless on any task should be deprecated. The only places it makes sense is in 1) targets (although you could put an <if/> inside the target itself) and 2) conditional subelements of tasks/datatypes like <exclude name="xyz.java" unless="abc"/>. For the later there is really no other way to do it. An interesting issue to think about is whether it makes sense to generalize if/unless to control whether an XML subtree is sent to a task or not. Jose Alberto -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
