Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Decides if Cargo should wait after the container is started or not. If using Cargo for integration tests, set it to false, otherwise Cargo will start the container and show the following message: Press Ctrl-C to stop the container...
Important: This parameter has been deprecated and will be removed soon. If you want to do manual testing, please use the cargo:run MOJO.

Top level configuration elements



Default value


Definition of a Configuration

(thumbs down)

Defaults to a standalone configuration if the container is of type local and a runtime one if it's of type remote


Definition of a Container

(thumbs down)

Defaults to a Jetty 7.x installed container if not specified


Definition of a Deployer

(thumbs down)

Defaults to a deployer matching the container's type if none is specified (installed local deployer for an installed container, remote deployer for a remote container and embedded local deployer for an embedded container)


A list of deployables that are going to be deployed in the container when it is started or when cargo:deploycargo:undeploy is called.

(thumbs down)

If the project's packaging is warear or ejb, the generated artifact is added automatically to the list of deployables to deploy. If you wish the generated artifact not to be added to the deployables list, just add an empty <deployer/> element.


Additional configuration that is used when deploying with the Cargo Daemon.

(thumbs down)

For more information, please read: Cargo Daemon.


Set this to true to bypass cargo execution

(thumbs down)

Defaults to false


(thumbs down)


titleThe wait parameter

Instead of tweaking your Maven project POM with the different values for the wait parameter, please use the cargo:run MOJO:

  • The cargo:start MOJO should be used to start the container and hand over to the next Maven execution; i.e. it should ONLY be used for integration testing.
  • The cargo:run MOJO will start the container and wait until the user decides to stop it by pressing CTRL + C, which implies that it should be used for manual testing.