I needed the ability to deploy to (i.e. configure) a container without starting it. This was so I could prepare a container locally that is to be archived and installed into a production environment. I wanted to use the same manner, and in fact the same Ant MacroDef, for configuring the container for production as I was for development and testing. The attached patch facilitates this by adding a "configure" action to the cargo task that doesn't attempt to start the container.
This patch is against http://svn.codehaus.org/cargo/extensions/tags/cargo-extensions-0.9/ant as I found the trunk to be binary incompatible with the 0.9 core uberjar.