We are missing this section in the documentation that documents how to manually provision external JGroups protocols to stacks managed by WildFly.

The easiest way to do this for a user is using maven get mojo followed by CLI command which sets up the external module.

We should strongly discourage people from modifying jgroups main module.xml as that hinders upgrade path.