Updated Branches: refs/heads/master d241b6a03 -> 1e8e82a97
Added docs about tracking forked execution Project: http://git-wip-us.apache.org/repos/asf/maven-surefire/repo Commit: http://git-wip-us.apache.org/repos/asf/maven-surefire/commit/1e8e82a9 Tree: http://git-wip-us.apache.org/repos/asf/maven-surefire/tree/1e8e82a9 Diff: http://git-wip-us.apache.org/repos/asf/maven-surefire/diff/1e8e82a9 Branch: refs/heads/master Commit: 1e8e82a97151a4d43e19bcac4052c7c8c3178be7 Parents: d241b6a Author: Kristian Rosenvold <krosenv...@apache.org> Authored: Wed Feb 12 07:45:51 2014 +0100 Committer: Kristian Rosenvold <krosenv...@apache.org> Committed: Wed Feb 12 07:46:10 2014 +0100 ---------------------------------------------------------------------- .../src/site/apt/developing.apt.vm | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/1e8e82a9/maven-surefire-plugin/src/site/apt/developing.apt.vm ---------------------------------------------------------------------- diff --git a/maven-surefire-plugin/src/site/apt/developing.apt.vm b/maven-surefire-plugin/src/site/apt/developing.apt.vm index 954f0ce..fb58a1f 100644 --- a/maven-surefire-plugin/src/site/apt/developing.apt.vm +++ b/maven-surefire-plugin/src/site/apt/developing.apt.vm @@ -65,6 +65,24 @@ mvn -Dsurefire.version=2.12 verify Load the source in your IDE, set a breakpoint at the start of ForkedBooter#main and attach a debugger to port 5005. +* Tracing forked execution + +The forked surefire process uses stdio to communicate back to the source. Sometimes when tracking troubles +it can be helpful to look at just the output of the fork. + +Ths can be done by running: + ++---+ +mvn -e -X install | grep Forking ++---+ + +If you copy the command part of the output, you should be able to re-run the command by just pasting it on +the command line (you might have to do only the bits after &&). + +You can now paste this command on the command line and capture the output of the fork. This may help you +determine if the problem is in the forked end or the receiving end. + + * TestCases All patches to surefire must contain test coverage, either as an integration test