Page Comparison

cargo:start

Start a container. That goal will:

• • If the plugin configuration requires so, installs the container (but will not call cargo:install).
  • If the plugin configuration defines a container with a standalone local configuration, it will create the configuration.
  • If the plugin configuration contains one or more deployables, it will deploy these to the container automatically.
  • If the plugin configuration contains no deployables but the project's packaging is J2EE, Java EE or Jakarta EE (WAR, EAR, etc.), it will deploy the project's deployable to to the container automatically.
  • And, of course, start the container.

Note: A container that's started with cargo:start will automatically shut down as soon as the parent Maven instance quits (i.e., you see a BUILD SUCCESSFUL or BUILD FAILED message). If you want to start a container and perform manual testing, see our next goal cargo:run.

cargo:run

Start a container and wait for the user to press CTRL + C to stop. That goal will:

• • If the plugin configuration requires so, installs the container (but will not call cargo:install).
  • If the plugin configuration defines a container with a standalone local configuration, it will create the configuration.
  • If the plugin configuration contains one or more deployables, it will deploy these to the container automatically.
  • If the plugin configuration contains no deployables but the project's packaging is is J2EE, Java EE or Jakarta EE (WAR, EAR, etc.), it will deploy the project's deployable to to the container automatically.
  • And, of course, start the container and wait for the user to press CTRL + C to stop.

cargo:stop

Stop a container.

cargo:restart

cargo:configure

Create the configuration for a local container, without starting it.

Note: If the plugin configuration requires so, the cargo:start goal automatically installs the container (but will not call cargo:install).

cargo:package

Package the local container.

Start a container via the daemon. Read more on: Cargo Daemon

Note: The daemon:start goal is actually equivalent to a restart in Codehaus Cargo's terms; in the case a container with the same cargo.daemon.handleid already exists then it will be stopped first before your container is started. This also implies that in the case the new container fails to start, the old one will not be restarted.

cargo:deployer-deploy (aliased to cargo:deploy)

Deploy a deployable to a running container.

Note: The cargo:start and cargo:run do already deploy the deployables specified in the configuration to the container; as a result calling cargo:deploy for a container which has been started by Codehaus Cargo in the same Maven project will most likely cause a second deployment of the same deployables (and might even fail).

cargo:deployer-undeploy (aliased to cargo:undeploy)

Undeploy a deployable from a running container.

cargo:deployer-start

Start a deployable already installed in a running container.

cargo:deployer-stop

Stop a deployed deployable without undeploying it.

cargo:deployer-redeploy (aliased to cargo:redeploy)

Undeploy and deploy again a deployable. If the deployable was not deployed before calling cargo:deployer-redeploy (or its alias cargo:redeploy) it will simply be deployed.

cargo:uberwar

Merge several WAR files into one.

cargo:install

Installs a container distribution, either downloaded using a URL or defined as a Maven artifact, on the file system.

Note: If the plugin configuration requires so, the cargo:start and cargo:run goals do automatically install the container (but will not call cargo:install).

cargo:help

Get help (list of available goals, available options, etc.).