The ManagementClient cannot be injected in in-container testing unless the jmx-as7 protocol is used. There is also an issue where the the class needs to be added to the deployment.

We need to get this working in the default protocol and REST protocol. The jmx-as7 protocol uses some outdated and MSC API's. We're running the risk of this protocol breaking and we need to explore updating or deprecating it. Actually, the jmx-as7 protocol has been updated. However, it doesn't work well with JUnit 5. We may need some improvements here or look more into the REST protocol.

One option might be to for wildfly-arquillian to create a feature pack which installs some built modules and has a DUP to add these modules. The catch with this approach would be that the feature-pack would need to be defined when provisioning a server and be more difficult to use on a downloaded server. This should be considered, but be a last resort.