> > > > The way I have done it so far is to only allow tasks to run > > async within the > > context of a single target. At the end of the target all task > > threads are > > joined and any exceptions in the individual threads are rethrown, > > potentially causing the build to fail. > > > > I think that is an appropriate level of async behaviour. > > > > Well this is where my comments about using ANT for more than > building comes > into play. The level of async that I am interested with is more > for testing > enviroments than for building environments. > > So imagine in conjunction with JUnit tests. Your test cases are executed > synchronously on the build, but you need to execute your server > application > in the background. You need to be able to start it, and > eventually stop it. > So on thise circumstances you really want a fork. > > The alternative is to provide scripts in all the different OSs > that you are > to call to just start and stop the server. I would like to use > ANT instead. >
This is exactly what I have done this for. <target test> <wlrun async="true" ... /> <sleep delay="10000"/> <junit .../> <wlstop .../> <join/> <echo message="test finished"/> </target>
