Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 76696 invoked from network); 16 Jan 2002 19:09:33 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 16 Jan 2002 19:09:33 -0000 Received: (qmail 18757 invoked by uid 97); 16 Jan 2002 19:09:04 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 18659 invoked by uid 97); 16 Jan 2002 19:09:02 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 18559 invoked from network); 16 Jan 2002 19:09:02 -0000 Message-ID: From: "Herman, Dave" To: "Ant Users List (E-mail)" Subject: if/unless? Date: Wed, 16 Jan 2002 11:21:18 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello, Would it be useful to add optional "if" and "unless" parameters to the task, so that you don't have to go through the rather ugly process of making a separate little target? For example, you can currently find yourself in a situation like this (unless there's a more elegant method I haven't thought of): But it might be nicer to be able to do: Or does this get into the ugly arguments about conditionals? Thanks, Dave H -- To unsubscribe, e-mail: For additional commands, e-mail: