Message-ID: <1842810525.298132.1368899398939.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_298131_128521680.1368899398938" ------=_Part_298131_128521680.1368899398938 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Cargo Maven = Plugin (and all other Cargo artifacts) are hosted at the Codehaus Maven rep= ository, which is synced to Maven central. = As Maven is configured for Maven central by default, no additional installa= tion or repository configuration is necessary to use the plugin.
There are also snapshot releases of the Cargo Maven plugin (and all other = Cargo artifacts) available through the Codehaus snapshot repository. Snapshot releases are= deployed automatically by the CARGO-deploy pla= n on the Codehaus Continuous Integration Server.
If you want use = snapshot versions of the Cargo Maven Plugin, you'll need to add this reposi= tory to your POM, settings file, or repository manager:
|<pluginRepository> and <r=
Note that you need to declare both t=
Then, you should decide which SNAPSHOT version to u= se. To find out what the latest SNAPSHOT version is, you can simply look at= the POM file for the Cargo Extensions= a>.
Finally, configure the Cargo Maven Plugin by specifying a SNAPSHO=
T version. For example, to use version
1.4.1-SNAPSHOT you woul=
d declare something similar to the following in your POM:
One important thing to understand is that this snaps= hot repository is managed by Nexus and is in fact a group of several reposi= tories (some proxied). Browsing the repository via the url would therefore = not display all files actually available, but only those cached in the Nexu= s instance. However, Maven will always be able to retrieve the latest snaps= hot release (as it reads the Maven metadata provided).------=_Part_298131_128521680.1368899398938--