that did the trick, thanks again! Now, what I thought might be a
better solution than using "var" was to create a "filelist" and add
files to this construct and then use it by ref in the upload target. I
thought creating an empty "filelist" then using it's refid to add
files might work, but it seems that it does not. I assume this is just
not how "filelist" works, any insights or alternative suggestions
welcome.
This is the code I was attempting:
in target#0 (main build target)
<filelist id="uploadList" dir=".">
</filelist>
in target#1 (if data translation happens)
<filelist refid="uploadList">
<file name="${dataOutFile}"/>
</filelist>
in target#2 (if compilation happens)
<filelist refid="uploadList">
<file name="${outputFile}"/>
</filelist>
in target#3 (upload target)
<filelist refid="uploadList" />
Regards,
Hudson
On Dec 11, 2007 10:59 AM, Hudson Ansley <[EMAIL PROTECTED]> wrote:
> yes, I am using <antcall> thanks so much for your explanation and
> suggestion - sounds like a winner!
> Regards,
> Hudson
>
>
> On Dec 11, 2007 10:56 AM, Peter Reilly <[EMAIL PROTECTED]> wrote:
> > You are most likely using <ant>or <antcall> to call the other targers
> > this causes a new ant project to be created. porjects created in or
> > modified in
> > the child projects have no effect on the properties in the main project.
> >
> > You can use <runtarget> from antcontrib to run the targets in the
> > same project.
> >
> > Peter
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
