forkMode is deprecated since Surefire 2.14

[gastaldi]

See "Migrating the Deprecated forkMode Parameter to forkCount and reuseForks" in https://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html

[geoand]

LGTM, but let's ask @Tibor17 to be certain

[famod]

Raises the question why just these two modules are not reusing forks.

[Tibor17]

@gastaldi
@geoand
@famod
Hey guys, the forkMode will be removed. It is one config parameter which has two meaning (reusability of JVMs and the number of threads executing parallel CLIs). We in Maven decided to split forkMode in two, means forkCount and reuseForks. You should not have a problem to use both instead of forkMode.

Feel free to ping us if there is another bug.

[Tibor17]

btw, the forkMode and forkCount + reuseForks appeared in the versions 2.x and forkMode was deprecated in 2.x several years ago. This is old story already.

[geoand]

Thanks for the info @Tibor17 !

[geoand]

Change makes sense but indeed it would be nice to know why we want no forking in this case

[famod]

@geoand Those two modules are forking but they do it for each test class (the fork of the previous test class is not reused).
Default is one fork per module that processes all test classes subsequently.

[geoand]

Ah, I didn't read the configuration correctly (on a phone).

I have 2 guesses:

1. they do so because it more closely resembles what a "function" does
2. there might be classloader issues when reusing these tests