Thanks for explaining this to me. I see your predicament. In v2, even though the domain has stopped, stop-domain command does not fail but return a message stating that domain isn't running. But in v3, the command actually fails and return a non-zero exit code. The job on Hudson failed because the command failed.
Can you open a bug on this?
How important is this bug? I don't think this can be fixed for Prelude. Is it okay if this is fixed on the v3 trunk?
[Message sent by forum member 'janey' (janey)]
http://forums.java.net/jive/thread.jspa?messageID=304189