Yesterday I did several changes to how Weld tests are run on WildFly. This applied to both master and 2.2:
1) No distinct profiles for WildFly 8 and 9 There is now only a single "incontainer" profile for both WildFly 8 and 9. This applies to the CDI TCK runner, integration tests (tests-arquillian) and probe integration tests (Weld 3.x only). To run the tests on wildfly run: > mvn clean verify -Dincontainer 2) No remote profiles Previously, the scenario for debugging in an application server was: - start WF manually (with debugger attached) - run a test with the remote profile The "incontainer" profile has been configured to allow connecting to a running WF instance. Therefore, the procedure for debugging is now: - start WF manually (with debugger attached) - run a test with the "incontainer" profile Jozef _______________________________________________ weld-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/weld-dev
