Content Comparison

<configuration>

Definition of a Configuration

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

<container>

Definition of a Container

Defaults to a Jetty 9.x installed local container if not specified

<deployer>

Definition of a Deployer

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)

<deployables>

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

If the project's packaging is war, ear 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.

<daemon>

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

For more information, please read: Cargo Daemon.

<skip>

Set this to true to bypass the executions of the Codehaus Cargo Maven 3 plugin.

Defaults to false, you can also steer it using the system property cargo.maven.skip


Set this to true to make the mojo ignore failures, so that Maven 3 can still progress through on integration tests with more than one container domain started.

Set this to true to not display the log message category prefixes, hence make the plugin's log messages shorterwhich could help diagnosing issues.

Since Codehaus Cargo Maven 3 Plugin version 1.10.11 onwards.