As you know, we are currently preparing CARGO 1.1.0. This new version
will bring in many changes, in particular changes in the way many of the
One discussion currently in progress is the cargo-maven2-plugin: the
current behaviour when starting a container is that CARGO starts the
container, and since its "wait" property is set to "true" by default it
will just show a message saying "Container started - Press CTRL + C to
Now, this behaviour is probably not the ideal when you want to use
cargo-maven2-plugin for integration testing: hence, the need to set the
"wait" property to "false" so that CARGO doesn't just wait once the
container but let other goals run (in particular, integration tests).
And, the question we're now asking is simple: whay not change this
default value to "false"; so by default the cargo-maven2-plugin starts
the container and then lets other tasks run?
Note that currently we do not plan changing the default behaviour of the
ANT tasks not the Java API.