>>>>> Steinar Bang <[email protected]>: > There is this output at the end of the "mvn clean install": > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project ukelonn.tests: Execution default-test of goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: The forked > VM terminated without properly saying goodbye. VM crash or System.exit called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_121\jre\bin\java" -jar > C:\Users\sbang\workspaces\ws06\ukelonn\ukelonn.tests\target\surefire\surefirebooter5197692333401719291.jar > > C:\Users\sbang\workspaces\ws06\ukelonn\ukelonn.tests\target\surefire\surefire8860295739440543272tmp > > C:\Users\sbang\workspaces\ws06\ukelonn\ukelonn.tests\target\surefire\surefire_05835872688929628334tmp"
> Obviously maven thinks the process has terminated. Just as obviously > there is still a java process running (that prevents delete of the > target\exam directory structure). The documentation says "With the Forked Container, the system under test runs in a separate Java virtual machine under remote control from the test driver." https://ops4j1.jira.com/wiki/display/PAXEXAM4/Pax+Exam How do I figure out whether I'm running a "forked container" or not? Is the mentioned "forked VM" in the rror message that has terminated, the VM actually running the tests? (ie. the single VM started in a "non-forked container" (or whatever it is called)...?). Or is the "forked VM" of the error message the front end that forks yet another VM to do the job, and it's this second VM that is left running? (ie. the "forked VM" of the error message is a VM started by maven surefire, and this VM runs a "forked container" that starts yet another VM where karaf is started and tests are run)
