Current(1.6.10) and previous version of cargo-maven2-plugin has some bad behaviour with wildfly12x+ containerId.
After starting, deploying, running tests, stopping container "content"-directory(with deployment artifacts like ears/wars) in profile(java.server.base.dir), lies directly in profile directory not under profile/data.
For example with jboss75x containerId content directory lies under data where it belongs.
See also Screenshots please.
The problem is. You can not start this profile manually without further adjustments. You must now move content to data.