I think I'll sit back and watch for a while... I still haven't seen Conor's thoughts on this (time zone difference) and since he wrote the parallel task to begin with, I'm interested to see his point of view.
> In the case of build exceptions (build failures), the standard answer is to > use a BuildListener which shutsdown > the server in case of a failure. Yes it requires programming from you, but it > could be as simple as executing an ANT target that runs the code to shutdown. I can do this. I was referring to the programming task of doing spawn, async, kill, join, sequential id="xxx", or whatever... > Well if you cannot contribute the work, you may need to wait for others to > have the time to contribute the code. That's what I've done so far. Not everyone has the luxury of time to devote to the programming side. Not a complaint, just the facts... > > 2. The Ant 1.4 documentation specifically uses the example > > of starting a server and running tests against it and > > stopping the server. If that is NOT what <parallel> is > > for, then better documentation and examples are in order... > > > > I never believed too much on those particular examples, to tell you the > truth. But I did not created that task. ;-) Well, as stated above, I'd like to see Conor's view, since he did create the task... And I believe I'm using it for what he had in mind when he created the task. > > > How do I 'check "tests.succesful" to verify if tests passed or not'? > > That sounds like scripting to me, and Ant doesn't have conditionals > > or branching... :^) See the smiley face - I was kidding. I use the paradigm you suggested all the time... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
