You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It really makes no sense to require a Jakarta EE server to support the Java SE CD APIs as it is a completely separate launch mode that would require a separate Arquillian container configuration. The userguide needs to be consistent with the WildFly/Weld jboss-tck-runner example.
The text was updated successfully, but these errors were encountered:
The userguide shows the following setup for the Web Profile:
and no example setup for the Full Platform. However, the jboss-tck-runner/pom.xml setup uses the following for the Web Profile:
and the following for the Full Platform:
It really makes no sense to require a Jakarta EE server to support the Java SE CD APIs as it is a completely separate launch mode that would require a separate Arquillian container configuration. The userguide needs to be consistent with the WildFly/Weld jboss-tck-runner example.
The text was updated successfully, but these errors were encountered: