Document the tck.arquillian.protocol.runnerPom system property

Signed-off-by: Scott M Stark <[email protected]>

tcks/profiles/platform/docs/userguide/platform/src/main/asciidoc/troubleshooting.adoc

@@ -37,6 +37,16 @@ Please verify that the property log.file.location exists in ts.jte
 Resolution: +
 You may have the `log.file.location` set in the ts.jte file, but if your Jakarta Persistence integration eagerly loads the testcase custom persistence provider, it may do so before the `log.file.location` property is set by the TCK harness code. To resolve this issue, you can set the `log.file.location` system property in your server configuration.
 
+* Problem: +
+When running the Jakarta Persistence TCK tests you see an error log message containing:
+
+[source,bash]
+----
+Failed to resolve protocol.jar. You either need a jakarta.tck.arquillian:arquillian-protocol-lib dependency in the runner pom.xml or a downloaded target/protocol/protocol.jar file.
+----
+
+The Arquillian protocol implementations used in the TCK add the jakarta.tck.arquillian:tck-porting-lib artifact automatically to the test deployment if the dependency exists in your runner pom. The code expects that the runner pom is named pom.xml. If you are using a different name or path, you will need specify a `tck.arquillian.protocol.runnerPom` system property in your surefire/failsafe plugin configuration to point to the correct pom file.
+
 [[support]]
 == Support
 

tcks/profiles/platform/docs/userguide/platform/src/main/asciidoc/using.adoc

@@ -55,10 +55,8 @@ As a general rule, the test runner should include the following:
 
 . Dependencies on the Junit5 and Arquillian test frameworks as shown in <<runner-maven-dependencies>>.
 . Configure your Arquillian container as shown in <<arquillian-container-configuration>>.
-.  Set the `TS_HOME` environment variable to the directory in which
-Jakarta EE {tck_version} Platform TCK was installed.
-.  Ensure that the `ts.jte` file contains information relevant to your
-setup. +
+.  Set the `TS_HOME` environment variable to the directory in which Jakarta EE {tck_version} Platform TCK was installed.
+.  Ensure that the `ts.jte` file contains information relevant to your setup. +
 Refer to <<setup-and-configuration>> for detailed configuration instructions, or that your runner maven project surefire/failsafe plugin has defined the equivalent system properties.
 .  Execute the `test` Maven goal to start the testsuite: +
 [source,bash]
@@ -168,6 +166,11 @@ You then need to define the specific dependencies for the test runner without th
     </dependencies>
 ----
 
+[NOTE]
+====
+The Arquillian protocol implementations used in the TCK add the jakarta.tck.arquillian:tck-porting-lib artifact automatically to the test deployment if the dependency exists in your runner pom. The code expects that the runner pom is named pom.xml. If you are using a different name or path, you will need specify a `tck.arquillian.protocol.runnerPom` system property in your surefire/failsafe plugin configuration to point to the correct pom file.
+====
+
 [[available-tck-test-artifacts]]
 ==== Available TCK Test Artifacts
 The list of groupId:artifactId for the Jakarta EE {tck_version} TCK test artifacts is: