Tibor17 edited a comment on pull request #240: URL: https://github.com/apache/maven-surefire/pull/240#issuecomment-680766589
@danberindei You'r right, the link does not work. We can update the HTML of course and fix it. The reason why the element is call it `forkNode` is the fact that it is still in a development. The initial idea was to call the fork JVM a node because there are user requirements to fork the JAR file in another place. Basically the tests may run in a distinct IP address, h/w, VM, etc. Therefore there is the name `node` because we may add more factories (where the `ForkNodeFactory ` is the first one) below the node itself and the test execution would become distributed over some nodes in your infrastructure. Imaging a factory which produces e.g. `ForkExecutor`. Currently we are building and executing a JAR in `target/surefire` for Nix systems and in temp directory for Windows by default. The user may change this behavior and distribute the execution to any h/w node, not only the local one as we know it right now. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
