Thanks for the pointer, Piotrek. It seems that using <jdkToolchain> in the configuration of the execution for the forked tests requires a local global toolchains.xml, but I was hoping to avoid the need for that, because nowadays toolchains:select-jdk-toolchain can auto-detect JDK toolchains (https://maven.apache.org/plugins/maven-toolchains-plugin/select-jdk-toolchain-mojo.html), and I would like to not force everyone working on these projects to have a local global toolchains.xml both locally and in their CI build environment.
Can you confirm that Surefire forking the Maven runtime JDK instead of the toolchain JDK is intentional behavior? If Surefire would do the latter, which is also what I expected it to do, then I wouldn’t need any additional configuration. Thanks, Nils. > Op 3 jan 2025, om 14:59 heeft Piotr Żygieło <piotr.zygi...@gmail.com> het > volgende geschreven: > > On Fri, 3 Jan 2025 at 14:47, Nils Breunese <n...@breun.nl> wrote: >> is there something I can do have it use the toolchain JDK for the forked >> tests > > https://maven.apache.org/surefire/maven-surefire-plugin/examples/toolchains.html > > -- > Piotrek > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
