If a configuration name is set to a value != standalone.xml, there is a failure when provisioning a bootable JAR. The bootable JAR expects the provisioned configuration file to be named standalone.xml

The option is correct, and is not in conflict with Bootable JAR packaging. There is a bug in the actual provisioning that must configure Galleon to provision a file named standalone.xml whatever the server configuration in use