On 4/19/07, Balasubramanian, Ravi Shankar <[EMAIL PROTECTED]> wrote:
Hi all, I did work on this and found that maven's java process is not waiting until all other processes started during the build is completed / terminated. Following is what I did:In one of my test cases, I start a new process using the java Runtime class. For experimentation I executed the command "notepad" on windows which would start a separate process for me. The test case is as follows: Process p = Runtime.getRuntime().exec("notepad"); When I do a mvn test, the java process started by the maven build does not exit until the notepad is closed or terminated. Is there a way or configuration in maven to work around such a setting or is maven designed like this? I might want to be starting a server like process in one of my test cases and would want maven to complete the build which currently is not happening.
Again, can you provide a thread dump log ? That will help us identify where maven hangs, and help us give you an answer. Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
