On 4/20/07, Balasubramanian, Ravi Shankar [EMAIL PROTECTED] wrote:
Hi,
Following is my test class that starts a notepad process from within:
public void startProcessNotepad() throws IOException {
Process p = Runtime.getRuntime().exec(notepad);
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
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
Hi,
Following is my test class that starts a notepad process from within:
public void startProcessNotepad() throws IOException {
Process p = Runtime.getRuntime().exec(notepad);
System.out.println(NOTEPAD STARTED);
}
When I execute this test
Just in case, if anybody is looking into this, I tried creating a new
java process from a simple Java class in it's main method and verified
if the main class exits. It does exit and only when I run it through a
test case in maven, the maven's java process is not exiting.
Regards,
Ravi
On 4/17/07, Balasubramanian, Ravi Shankar [EMAIL PROTECTED] wrote:
Hi all,
We use maven-surefire-plugin to run our testng test cases. I encountered
a problem where in the maven VM is hanging when one of the test cases
start a separate java process from within it using the java
ProcessBuilder
