we're setting up a project which uses JBoss 7.1.0.Final as container. Therefore we created a standalone configuration using cargo, which correctly installs the container but fails on startup with the following message:
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.0:run (default-cli) on project cargo.jboss71: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.0:run failed: Cannot modify XML file C:\temp\cargo.jboss71.test\target\cargo\configurations\jboss71x/configuration/standalone.xml: Node //server/socket-binding-group/socket-binding[@name='jmx-connector-registry'] not found in file C:\temp\cargo.jboss71.test\target\cargo\configurations\jboss71x/configuration/standalone.xml -> [Help 1]
It seems that cargo tries to change a node in the JBoss descriptor which does not exist. Currently we implemented a workaround by providing a standalone.xml which contains the missing information.
The problem can be reproduced by running "mvn install cargo:run" using the attached pom.xml.