Message-ID: <751584674.39808.1371536327128.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_39807_151072604.1371536327127" ------=_Part_39807_151072604.1371536327127 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
mvn --version" at a command prompt. =09
core/samplesbuilds require that version of Maven
|Maven 3 support|
CARGO 1.0.x's Maven 2 plugins do work very well with Maven 3, but CARGO = 1.0.x requires Maven 2 for its build process. Starting from CARGO 1.1.x, CA= RGO also builds on Maven 3, see CARGO-789: Make build = work with Maven 3.0.
|First time build|
The Cargo build contains functional tests. Those tests are run on differ=
ent containers. The first time you build Cargo it will download those conta=
iner distributions which will take some time (the containers are installed =
CARGOHOMEand type "
mvn install= ". This will build the full Cargo project.
CARGOHOM= Eand type "
The default list of containers to run on depends a property cargo.contai= ners defined in CARGOHOME/core/samples/pom.xml. It can also be supplied at = the commandline by using profiles (-P<containerId>).
For example if you only want to run on Tomcat 5.x you'd write:
-Ptomcat5x clean install
There are also some multi-container profiles, for example
l-downloadable clean install will build CARGO and test the CARGO sam=
ples with all downloadable containers (Jetty's many versions, Tomcat's many=
mvn -oto work offline. This improves the build sp= eed as Maven 2 does not check for updates on the remote repository for SNAP= SHOTs.
If you need to build cargo from behind a proxy, proceed as follows:
.m2/settings.xmlfile from your home directory= (C:/Documents and Settings/username on Windows),