Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: domain of
 prvs=539652388c=shawn.castrianni@halliburton.com designates 34.254.247.12 as
 permitted sender)
From: Shawn Castrianni <Shawn.Castrianni@halliburton.com>
To: "'ivy-user@ant.apache.org'" <ivy-user@ant.apache.org>
Date: Mon, 25 May 2009 17:29:48 -0500
Subject: ivy buildlist task
Thread-Topic: ivy buildlist task
Thread-Index: AcndiE9AKzTgi+wTR6mOTu3jJK4syg==
Message-ID: 
 <34721A41A7BCF54ABC3B116219A8C1C205752571A4@NP1EXCH012.corp.halliburton.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_34721A41A7BCF54ABC3B116219A8C1C205752571A4NP1EXCH012cor_"
MIME-Version: 1.0

--_000_34721A41A7BCF54ABC3B116219A8C1C205752571A4NP1EXCH012cor_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"

I am trying to programmatically build up a list of build.xml files to pass =
into the ivy:buildlist task.  My problem is that since this is generated dy=
namically, I don't know how to create a dynamically generated fileset to pa=
ss to the buildlist command.  If all build.xml files had a common parent di=
rectory, then I could create an includes property dynamically and then spec=
ify a single fileset with the common parent directory and the dynamically g=
enerated includes property.  However, I can't guarantee that all build.xml =
files will have a common parent directory.  I would normally accomplish thi=
s with multiple filesets, but that cannot be done dynamically.  Therefore, =
the only thing I can think of is to enhance the buildlist command and allow=
 a path to be specified along with a fileset.  A path can dynamically be ge=
nerated since a path can be appended to using the refid AND a path does not=
 enforce a single common parent directory for all build.xml files.

Any ideas?

---
Shawn Castrianni

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and pri=
vileged information for the sole use of the intended recipient.  Any review=
, use, distribution, or disclosure by others is strictly prohibited.  If yo=
u are not the intended recipient (or authorized to receive information for =
the intended recipient), please contact the sender by reply e-mail and dele=
te all copies of this message.

--_000_34721A41A7BCF54ABC3B116219A8C1C205752571A4NP1EXCH012cor_--