Hi John, Have you used the version 3.0.0-M4? There were important fixes for Java 11/Linux (alt. Docker). The message "The forked VM terminated without properly saying goodbye." is too general error message. Can you post the configuration of the plugin with the latest version in your POM including the test summary? What provider you use?
Cheers Tibor17 On Sat, Aug 31, 2019 at 7:53 PM John Patrick <[email protected]> wrote: > evening, > > i'm having trouble testing a multi-release jar project using > toolchains. i want to test it using both java 1.8 and java 11. > > i've the following structure; > src/main/java > src/main/java11 > src/test/java > src/test/java11 > > tried both maven-surefire-plugin v 2.22.2 and 3.0.0-M3 > > if i set java to 1.8 and do mvn clean install, everything works but it > uses java 1.8 for the testing. > > if i set java to 11 and do maven clean install, it fails starting surefire. > > [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: > The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > [ERROR] Error occurred in starting fork, check output in log > [ERROR] Process Exit Code: 1 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669) > > How can I test using java 1.8 then execute tests again using java 11. > > What profile or toolchain settings can i configure so for a surefire > execution it uses the java version i choose? > > John > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
