Community
Participate
Working Groups
Right now, after the remote VM is terminated, the debugging in eclipse is terminated as well. It would be useful to be able to force it to stay alive. Use case I am facing now: Nondeterministically a test fails to be loaded, so in order to catch such behaviour in debug mode, I need to run debugging on all of the tests we have to have a chance to reproduce that behaviour. They however run in many testsuites and Eclipse keeps disconnecting after each of them.
Matej - to be precise you are running the tests from maven which you have configured to launch each testsuite in a separate process, correct ? And yes, I think this would be a great feature for all those that are forced to run each test in a new vm. would be great to have a launch go back to listening when the debugged client exit.
Max - not sure, I am using only defaults "mvn clean install -Dmaven.surefire.debug", however I am running multiple maven modules
yeah so each test run default to forking (see http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html) As a workaround you can try run with 'mvnDebug -DforkCount=0 clean install' to avoid the launching (but your tests might rely on it being launched separately) still find this feature request interesting for the cases where you do have multiple launches and need it.
In my case -DforkCount=0 will cause problems because the system is not stable when being tested (didn't investigate deeper why it happens).
