Details
Description
The maven2 cargo plugin keeps track of a container which it creates in the global Maven context, preventing multiple containers from being run at once (CARGO-421). To store containers properly in the Maven context, each container created needs a unique identifier which can be specified in the configuration.
You can see our fix in the attached patch file (against HEAD), and why it isn't ideal. I've also included a test case which passes after the patch is applied.
committed into svn head