Return-Path: <jwalters@netnumina.com>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 59712 invoked from network); 13 Dec 2000 14:54:33 -0000
Received: from relay1.netnumina.com (198.3.137.251)
  by locus.apache.org with SMTP; 13 Dec 2000 14:54:33 -0000
Received: by relay1.netnumina.com with Internet Mail Service (5.5.2650.21)
	id <Y3BS3T1A>; Wed, 13 Dec 2000 09:54:34 -0500
Message-ID: <B7800B02C98FD4118E8000D0B7820F4A0D1BE2@mabost01.netnumina.com>
From: Jay Walters <jwalters@netnumina.com>
To: "'ant-dev@jakarta.apache.org'" <ant-dev@jakarta.apache.org>
Subject: RE: Expanding ${} constructs for all attributes
Date: Wed, 13 Dec 2000 09:54:46 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

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 ...

Cheers
Jay Walters

-----Original Message-----
From: Peter Donald [mailto:donaldp@apache.org]
Sent: Wednesday, December 13, 2000 9:11 AM
To: ant-dev@jakarta.apache.org
Cc: ant-dev@jakarta.apache.org
Subject: Re: Expanding ${} constructs for all attributes


At 09:04  13/12/00 -0500, Rousseau, John wrote:
>We have a bunch of stand-alone commands we create around our main
>product. Not all of these commands are built/supported on all
>platforms (it's native code). What I want to do is have a
>targets.xml file with build rules for all targets. I then want a
>master build.xml file for each platform that sets ${build.targets}
>appropriately for that platform, and calls <ant> on the targets
>file. The targets file main <target> then depends on
>${build.targets}. This is a serious lack of functionality when
>compared to make.

nope you can do that fine in vanilla ant now. ie add this into file

<target name="do-targets" depends="target1, target2 target 3" />
<target name="target1" if="do-target1" />
<target name="target2" if="do-target2" />
<target name="target3" if="do-target3" />

then call that file either setting or not setting the respective properties
do-target1, do-target2, do-target3. Much easier to comprehend IMHO and
easier to read/maintain.


Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*