The concurrency TCK runner creates directory target/wildfly/tck-libs and popluates it with various artifacts. It then uses the CLI to configure WildFly to use that dir as an ee subsystem 'global-directory'.
This works fine when the WildFly installation being tested is located at target/wildfly. But if env var JBOSS_HOME is set, then the WF installation can be anywhere, and the tck-libs dir may not be under its root. This leads to TCK failures where the path pointed to by the ee subsystem 'global-directory' doesn't exist.
Solution is to change the ee subsystem 'global-directory' setting to use 'user.dir' as the relative-to value, and "target/wildfly/tck-lib" as the path. The user.dir path points to the CWD from which maven is running.
The concurrency TCK runner creates directory target/wildfly/tck-libs and popluates it with various artifacts. It then uses the CLI to configure WildFly to use that dir as an ee subsystem 'global-directory'.
This works fine when the WildFly installation being tested is located at target/wildfly. But if env var JBOSS_HOME is set, then the WF installation can be anywhere, and the tck-libs dir may not be under its root. This leads to TCK failures where the path pointed to by the ee subsystem 'global-directory' doesn't exist.
Solution is to change the ee subsystem 'global-directory' setting to use 'user.dir' as the relative-to value, and "target/wildfly/tck-lib" as the path. The user.dir path points to the CWD from which maven is running.