Return-Path: Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 64163 invoked by uid 500); 15 Jul 2003 14:50:02 -0000 Mailing-List: contact user-help@ant.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 user@ant.apache.org Received: (qmail 64147 invoked from network); 15 Jul 2003 14:50:02 -0000 Received: from mr-mcfeeley.fgm.com (216.1.16.101) by daedalus.apache.org with SMTP; 15 Jul 2003 14:50:02 -0000 Received: from fgm.com (hades.fgm.com [216.1.16.126]) by mr-mcfeeley.fgm.com (8.11.6/8.11.2) with ESMTP id h6FEiBm26991; Tue, 15 Jul 2003 10:44:11 -0400 Message-ID: <3F14149C.6010508@fgm.com> Date: Tue, 15 Jul 2003 10:50:04 -0400 From: Daniel Barclay User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ant Users List Subject: why not conditions on tasks as on targets? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Why do tasks not have if and unless attributes as targets do? It seems that _always_ having to put tasks in separate targets to use condition checks creates unnecessary complexity (multiple targets to get just one job done). Thanks, Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org