ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Lévy-Lambert <>
Subject AW: Killing Forked JVMs (was RE: Killing Forked Jams)
Date Fri, 12 Sep 2003 19:40:19 GMT
The parallel task might be useful for you :

from the documentation : ( )
  <wlrun ... >
    <sleep seconds="30"/>
    <junit ... >

This example represents a typical pattern for testing a server application.
In one thread the server is started (the wlrun task). The other thread
consists of a three tasks which are performed in sequence. The sleep task is
used to give the server time to come up. Another task which is capable of
validating that the server is available could be used in place of the sleep
task. The test harness is then run. Once the tests are complete, the server
is stopped (using wlstop in this example), allowing both threads to
complete. The parallel task will also complete at this time and the build
will then continue.


-----Urspr√ľngliche Nachricht-----
Von: Gardner, Chris []
Gesendet: Freitag, 12. September 2003 15:24
An: 'Ant Users List'
Betreff: Killing Forked JVMs (was RE: Killing Forked Jams)

My spell checker changed JVM to JAM.  Sorry.

-----Original Message-----
From: Gardner, Chris [
<> ]
Sent: Friday, September 12, 2003 9:21 AM
To: ''
Subject: Killing Forked Jams

Is there a built-in mechanism in ant to kill forked Jams?  In my case,
I'm using <java fork="true"> to launch a server process that I run tests

against.  This server process is a small, specialized http server
( that has no accompanying ant tasks.  I have to fork
the JAM because the server process depends on the value of the dir
attribute of <java>.  When the tests are finished, the build does not
finish because it is waiting on the forked JAM to complete.

I don't want to use the <java> timeout attribute because I have no way
of knowing how long those tests will take.

Any suggestions?



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message