I took a quick look at cactus but it appears to be more of a unit test tool, not a launcher. Although I am very interested in a more generic launching process like the fellow mentioned below.....
thanks,
don.
-----Original Message-----
From: Peter Donald [mailto:[EMAIL PROTECTED]]
Sent: Saturday, June 16, 2001 5:01 AM
To: [EMAIL PROTECTED]
Subject: Re: Ant 1.3 sequence of tasks but would like concurrent?
On Sat, 16 Jun 2001 01:11, McNamara, Sean (Contractor) wrote:
> Thanks for your response Stefan. Yes, the misuse of TASK for TARGET was a
> mistake, and if my description wasn't correct, my impression of the v2.0
> mutlithreading (based on your description) was.
>
> Question: Since multithreading of targets as you've described it still
> wouldn't address the issue of executing completely standalone,
> non-returning processes, is this something that will be addressed in
> another way?
>
> In particular, I'm looking for a way to launch a process like an
> application server, that requires a JVM, but whose JVM never exits
> (weblogic being a good example.) This can be done by writing a shell
> script to launch the application server as a background process, but doing
> so ties the build to the platform for which the launch script was written.
> Is there a planned way to give users this ability, or is there already some
> way to do this that I'm simply not understanding?
>
> Thanks for your help!
Check out the commons subproject "cactus". It launches different applications
this way and may be of use to you.
