Hi, I've never used it but it the debug remote java application launch configuration there is an option to listen to jvm (connection type : standard( socket listen) ) . Presumably the forked jvms will attached themself to the debugger contrary to the usual case where the debugger is attached to the jvm.
On Tue, Aug 12, 2014 at 2:35 AM, salilsurendran <salilsurend...@gmail.com> wrote: > Hello, > Due to legacy reasons we have forkMode set to 'pertest' in our pom. > This > configuration can't be changed. However when I remote debug in eclipse(or > command line) I use `"-Dmaven.surefire.debug="-Xdebug > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Xnoagent > -Djava.compiler=NONE" test -DforkMode=never"`. I then connect to port 8000 > from eclipse. However since forkMode is set to pertest each time a jvm is > spawned to run a test which means that I have to remote connect every time > to keep the test running and I have over 3000 tests. The -DforkMode=never > never takes effect and is overridden with what is the in the pom. Is this > the right behavior? What can I do to have the remote debugger reconnect > even > if the jvm forks? > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Have-to-reconnect-each-time-while-running-debugging-maven-remotely-tp5802153.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Adrien Rivard
