...
Yes, you've read it right, there's no <configuration> element in this example! When you use this setup the Cargo m2 Maven 3 plugin will use a Jetty container by default. You can start the container with mvn cargo:start and stop it with mvn cargo:stop.
...
If your project is a J2EE, Java EE or Jakarta EE project (i.e. of type <packaging>war</packaging>, <packaging>ear</packaging>, <packaging>ejb</packaging> or <packaging>uberwar</packaging>) and you use the Cargo m2 Maven 3 plugin on that project then the generated artifact will be automatically added to the list of deployables to deploy. You can control the location of the artifact by using the <location> element (it defaults to ${project.build.directory}/${project.build.finalName}.${project.packaging}). In addition if you want to wait for the deployment to be finished you can specify a <pingURL> (none is used by default). Here's an example:
...