ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kim1 <kim...@gmail.com>
Subject how to ensure that paths are carried through when using nested ANT scripts
Date Thu, 20 May 2010 05:57:11 GMT

Hi there.

I have an interesting situation with an ant script I am working on.
There are 3 scripts in total:
(1) Main File Copying script
(2) Error message script

and now I have been given a requirement to put a wrapper script (3) around
the existing Main File Copying script. I have numbered them for readability
sake.

Script 1 contains targets that are run in a sequence using the depends task,
with the exception of when a log file is required, then it will use
runtarget to run a target in script 2.

This all works fine.

Now I have been asked to create another script to basically call the file
copy script (1).  This will allow one to do this task asynchronously without
having to wait for the outcome and still get things like error messages
created.
However, when I do so - then runtarget on the error message target doesn't
work - it can't find the error message target - seemingly because the file
import hasn't been executed by this script as its a top level component (and
we are only calling a target in the script).

Should I use antcall instead? I've heard nasty things about it! Can I ensure
the existing properties are carried across with runtarget? I'm still
learning - but aren't we all/!

Cheers
K


-- 
View this message in context: http://old.nabble.com/how-to-ensure-that-paths-are-carried-through-when-using-nested-ANT-scripts-tp28617478p28617478.html
Sent from the Ant - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message