Message-ID: <839938623.2471.1406094694501.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2470_204103726.1406094694501" ------=_Part_2470_204103726.1406094694501 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Cargo Maven Plugin is found at (groupId:artifactId) org.codehaus.car= go:cargo-maven2-plugin. This plugin works with both Maven 2.x and 3.x.
The Cargo Maven Plugin (and all other Cargo artifacts) are hosted at the= Codehaus Maven repository, which is synced to = Maven central. As Maven is configured for Maven central by default, no = additional installation or repository configuration is necessary to use the= plugin.
There are also snapshot releases of the Cargo Maven plugin (and all othe= r Cargo artifacts) available through the Codehaus snapshot repository. Snapshot releases a= re deployed automatically by the CARGO-deploy p= lan on the Codehaus Continuous Integration Server.
If you want use snapshot versions of the Cargo Maven Plugin, you'll need= to add this repository to your POM, settings file, or repository manager:<= /p>=20 =20
Then, you should decide which SNAPSHOT version to use. To find out what = the latest SNAPSHOT version is, you can simply look at the POM file for the Cargo Extensions.
Finally, configure the Cargo Maven Plugin by specifying a SNAPSHOT versi=
on. For example, to use version
1.4.9-SNAPSHOT you would decla=
re something similar to the following in your POM:
One important thing to understand is that this snapshot reposito= ry is managed by Nexus and is in fact a group of several repositories (some= proxied). Browsing the repository via the url would therefore not display = all files actually available, but only those cached in the Nexus instance. = However, Maven will always be able to retrieve the latest snapshot release = (as it reads the Maven metadata provided).