Guijarro, Julio wrote: > We don't have any command line tool to do that but it would not be difficult > to add one. > > You could have a component that registers itself with the Termination Hooks > and then either sends you a notification or terminates itself (and, and for > example, you block on it until it terminates). > > The termination hook sends information about the name of the component that > has terminated and its termination record.
The test compounds (TestBlock, TestCompound) can send out events to listening processes, they notify when they start and stop, and when tests underneath finish. This is how I bridge from junit to test runs (look at org.smartfrog.test.DeployingTestBase in testharness/src) I was actually thinking of doing some work on those to superclass the test events with a generic 'build event', so that I can have other 'builders' that do work in a build workflow can feed events to a general listener. Ideally with some percentage done/estimate time remaining data, though that's really hard to get right. With something like that formalised, it'd be easy enough to have an ant task and command line script to block until something reaches a desired state, terminates or a timeout kicks in. -steve ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Smartfrog-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/smartfrog-users
