Thanks. Using spawn it worked!
RADEMAKERS Tanguy wrote:
Hello,
Just off the top of my head, but did you look into using the spawn
attribute of the exec task?
Regs,
/t
-Original Message-
From: swapnil_r_84 [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 11:21 AM
Earlier I was using some other build tool to build my project. Here if a target
is built and if the same target is used to build some other target, it compares
the timestamp and will not build the dependent targets again.
As I started working on ANT, I found it very useful and intersting. But in
query wrote:
Earlier I was using some other build tool to build my project. Here if a target
is built and if the same target is used to build some other target, it compares
the timestamp and will not build the dependent targets again.
Ant doesnt compare the timestamps on targets, but it
As you have mentioned, time stamp comparision will be done at the task level
tasks like lt;javacgt;. But in a target, I will be defininig many tasks like
lt;javacgt;,lt;execgt;,lt;javagt;,lt;mkdirgt;,lt;copygt;,lt;deletegt;,lt;cvsgt;
etcSo my concern is instead of repeatedly checking the
--- Steve Loughran [EMAIL PROTECTED] wrote:
query wrote:
Earlier I was using some other build tool to build
my project. Here if a target is built and if the
same target is used to build some other target, it
compares the timestamp and will not build the
dependent targets again.
Ant
On Thu, 24 May, 2007 12:46 pm, query wrote:
Earlier I was using some other build tool to build my project. Here if a
target is built and if the same target is used to build some other target,
it compares the timestamp and will not build the dependent targets again.
As I started working on ANT,
Joe Schmetzer wrote:
On Thu, 24 May, 2007 12:46 pm, query wrote:
Earlier I was using some other build tool to build my project. Here if a
target is built and if the same target is used to build some other target,
it compares the timestamp and will not build the dependent targets again.
As I
Hi
I have a requirement wherein I need to make sure the
process doesnt exist. So I need to do something like
this -
`netstat -tln | grep 8080 | cut -f1 -d'.
If the return value of the above is tcp, then i know
that a process is running . I need to run this
command in a loop until the
I may be being a bit picky but I would not key on a port (which could
change in a config file) I would target the process name itself with ps
or pgrep myself.
I haven't done any serious ant dev in a while (my build scripts work
fine =) but if you have exhausted the core and contrib tasks then
There is socket to check for ports, but no while. I would suggest
using scriptdef and write it in a code.
- Alexey.
Krish wrote:
Hi
I have a requirement wherein I need to make sure the
process doesnt exist. So I need to do something like
this -
`netstat -tln | grep 8080 | cut -f1 -d'.
If
Please also look for retry task in this mailing list.
- Alexey.
Alexey N. Solofnenko wrote:
There is socket to check for ports, but no while. I would suggest
using scriptdef and write it in a code.
- Alexey.
Krish wrote:
Hi
I have a requirement wherein I need to make sure the process
Two things:
Ant will show the task as being executed, but may not actually carry
out the task. For example, you may see a task copy being executed
when you have the debug flag on, but the copy itself might not be
done. Of course, a target will always be executed even if the tasks in
it don't
Why not write a shell script and then have the shell script execute
the loop? All the exec task would have to do is execute the shell
script. The shell script can return a non-zero exit code on failure.
On 5/24/07, Krish [EMAIL PROTECTED] wrote:
Hi
I have a requirement wherein I need to make
13 matches
Mail list logo