We currently use client dependencies from Maven for the core profile TCK tests. This is fine as we generally keep dependencies in sync with that is in WildFly. However, we can use the additionalClasspathElement configuration with the surefire and failsafe plugins in combination with the ant-maven-plugin to set a path property.
We currently use client dependencies from Maven for the core profile TCK tests. This is fine as we generally keep dependencies in sync with that is in WildFly. However, we can use the
additionalClasspathElement
configuration with the surefire and failsafe plugins in combination with the ant-maven-plugin to set a path property.