Well, I'm not sure how one calls another whole script, perhaps someone
else reading this does.
However, if they are all typical build scripts in the sense that there
is one particular target that is called to get things going, you can
certainly antcall that target in each of the scripts. That would have
the desired effect I believe. If you have the luxury of modifying the
scripts a bit, you can certainly ensure this is the case, and you should
be good to go. When you antcall from the one "base" script, control
will return there wheen the other script completes, so no problem doing
that a bunch of times.
Frank
THUFIR HAWAT wrote:
On 7/30/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
...
Executing build.xml results in the test2 target being executed after
test1 is. The project name has to be different, although what you get
looks more like a warning than an error to me, but that's the reason it
is different above.
Is that what you meant?
Frank
...
ok, there's build.xml and build2.xml, both in the same directory.
What I want is for build.xml to do it's thing and then "call"
build2.xml and when build2.xml completes its task, return to where
build.xml left off.
build.xml itself wouldn't really be doing anything at all, but calling
build2.xml, build3.xml, etc. All the work is being done in
build[n].xml, so to speak.
Can that be done with antcall, or is something else required?
thanks,
Thufir
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
