From d68d0ef2ec8c88edc44aefbfb4bc14f762e5e8bd Mon Sep 17 00:00:00 2001
From: Mathias Fussenegger <f.mathias@zignar.net>
Date: Wed, 27 Sep 2023 15:25:22 +0200
Subject: [PATCH] Mention toolchains limitations in docs

If forkCount is configured the test goal can fail with a
UnsupportedClassVersionError

Apparently this is by design:

    https://issues.apache.org/jira/browse/SUREFIRE-720?focusedCommentId=16395576&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16395576

The documentation should mention a limitation like that.
---
 maven-surefire-plugin/src/site/apt/examples/toolchains.apt.vm | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/maven-surefire-plugin/src/site/apt/examples/toolchains.apt.vm b/maven-surefire-plugin/src/site/apt/examples/toolchains.apt.vm
index 891f8b1135..51799daa54 100644
--- a/maven-surefire-plugin/src/site/apt/examples/toolchains.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/examples/toolchains.apt.vm
@@ -36,6 +36,9 @@ Using Maven Toolchains with ${thisPlugin}.
     guide, ${thisPlugin} will launch the test jvm using the main toolchain
     configured in Maven.
 
+    Note that options like <<<forkCount>>> prevent the toolchains from being used.
+    See {{{https://issues.apache.org/jira/browse/SUREFIRE-720}}SUREFIRE-720} for more information.
+
     In some cases, it may be desirable to compile and test using different jvms.
     While the <<<jvm>>> option can achieve this, it requires hardcoding system-specific paths.
     Configuration option <<<jdkToolchain>>> can be used to supply an alternate toolchain specification.