Return-Path: <JFernandez@viquity.com>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 14415 invoked from network); 13 Dec 2000 21:32:51 -0000
Received: from postbox.viquity.com (HELO dcsrv0.ecom2ecom.com)
 (63.198.126.137)
  by locus.apache.org with SMTP; 13 Dec 2000 21:32:51 -0000
Received: by dcsrv0 with Internet Mail Service (5.5.2650.21)
	id <YL05WS2X>; Wed, 13 Dec 2000 13:31:20 -0800
Message-ID: <635802DA64D4D31190D500508B9B04104E1018@dcsrv0>
From: Jose  Alberto Fernandez <JFernandez@viquity.com>
To: "'ant-dev@jakarta.apache.org'" <ant-dev@jakarta.apache.org>
Subject: RE: Expanding ${} constructs for all attributes
Date: Wed, 13 Dec 2000 13:31:18 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

> From: Jay Walters [mailto:jwalters@netnumina.com]
> Sent: Wednesday, December 13, 2000 6:55 AM
> To: 'ant-dev@jakarta.apache.org'
> Subject: RE: Expanding ${} constructs for all attributes
> 
> 
> This gets back to my issue (I know you've already decided 
> against it, relax,
> the truth will set us all free.)
> 
> The mutual exclusivity of the properties do-target1, do-target2 and
> do-target3 is your responsibility as the programmer.  Now 
> maybe we can write
> an optional ANT task ...
> 

A couple of months ago I wrote a <case> task, that allowed you to inspect
the value of a property and set another property depending on it.
But it was sutdown, as not worthy, too scripty :-(

In any case, the accepted procedure is using the pattern:
   <property name="X.${X}" value="true" />
   
   <task .... if="X.A" .../>
   <task .... if="X.B" .../>

and so on.

Hope this helps,

Jose Alberto