This page last changed on Nov 03, 2010 by alitokmen.
Mission
Cargo is a thin wrapper that allows you to manipulate Java EE containers in a standard way.
Tools
Cargo provides the following Tools and APIs:
- A Java API to start/stop/configure Java Containers and deploy modules into them.
- A Java API to parse/create/merge Java EE Modules
- Ant tasks, Maven 1, Maven 2 plugins.
- Intellij IDEA and Netbeans plugins are in the sandbox.
Usage
Cargo is often used to deploy applications to containers from ant or maven builds. Cargo can install the container and dependencies needed for your deployment as well. Click here for a Maven 2 quick start!
For more use cases, please check the utilisation page.
Development Status
Current Versions
click in the status column to get release notes:
Version |
Status |
Comments |
1.0.4 |
|
Released on 03/11/10 |
All released versions are available here.
Container Support
List of supported containers and the extensions that are implemented for each container (Java API, Ant tasks and Maven plugins). The specified version is the version of the associated Cargo module where the feature was first made available (for example 0.2 for the Maven2 plugin means version 0.2 of the Cargo Maven 2 extension release). Click on a container's name to see a detailed list of features it supports.
We also encourage you to report success and failures on different versions of those containers in the Tested on section.
News
CARGO 1.0.4 released!
Hello, CARGO enthusiasts!
We are happy to announce the immediate availability of CARGO 1.0.4. This new version comes with 26 bug fixes, improvements and bug fixes, here is a short summary of the most interesting ones:
- The Apache Geronimo container is back again! Both versions 1.x (these are more than 4 years old, now!) and 2.x are supported, please see the documentation pages on http://cargo.codehaus.org/Geronimo+1.x and http://cargo.codehaus.org/Geronimo+2.x (I'll not list the JIRA tickets here, we have many of them!)
- Added support for the OSGi Bundle deployable type (CARGO-850 and some others). Currently, only the OW2 JOnAS 5.x container can handle bundles, hopefully that list should expand with the new versions of GlassFish and Geronimo.
- Made the new JBoss deployers, introduced in CARGO 1.0.3, work with big (tens of megabytes) files (CARGO-859); which actually is the filesize of real-life applications
- Various documentation updates (Documentation for pingTimeout, JBoss naming ports, missing property names, etc.)
- Made the FILE deployable actually support all types of files
- ... and more!
We have also finely tuned our release process, and CARGO 1.0.4 is the first CARGO version ever that has been tagged, staged, checked for quality and voted for during 72 hours before being released. Bravo, team! 
CARGO users that prefer the Java API and/or the ANT tasks can download this new version via http://cargo.codehaus.org/Downloads
Those who use the Maven2 plugin simply have to change their plugin version in their POMs -the artifacts are already on the Maven2 central repository.
Also, I will be sending nice e-mails on various application servers' mailing lists in order to introduce them CARGO. The current version can be seen on the "let's make some noise" page and all comments, corrections and ideas are most welcome.
Enjoy this new release!
CARGO 1.0.3 now available !
Hello CARGO enthusiasts,
6 weeks after CARGO 1.0.2, CARGO 1.0.3 has been released. That new version comes with 28 bug fixes and various improvements, in particular attention has been paid to remote containers:
- In the "CARGO samples", which run many tests on various containers and therefore guarantee a certain level of quality, we have re-enabled the testing of all Remote containers (CARGO-818).
- For a long (looooong) time, the CARGO JBoss remote deployer could not actually deploy to remote servers: it was expecting the file to deploy to be accessible by the JBoss server (which is possible using technologies like NFS, but that's not natural is it?). With CARGO 1.0.3, the JBoss remote deployer can upload and deploy your applications remotely on your JBoss server (versions 4.0.x, 4.2.x, 5.0.x, 5.1.x and 6.0.x). Read more here: http://cargo.codehaus.org/JBoss+Remote+Deployer, issue link here: CARGO-416
- On Jetty, the deployer helper application's path has been set to /cargo-jetty-deployer (it used to be the WAR's name, which contains version number and other non-determinictic data) (CARGO-820).
- On JOnAS, remote authentication issues have been corrected (CARGO-836) and the CARGO JOnAS deployer now supports the "development" mode (available since JOnAS 5) (CARGO-838).
- The Tomcat 7 remote deployer has been fixed (CARGO-817).
Moreover, CARGO 1.0.3 fixes other issues and adds interesting functionalities, of which:
- The Maven2 plugin now has a "skip" element for skipping CARGO (CARGO-481). That property can also be passed via a system environment variable.
- Fixed the MANIFEST of the WAR generated by CARGO uberwar (CARGO-727).
- Stopping the container does not longer corrupt the output file (CARGO-520).
Finally, we have also started a big move under the hood: move to Nexus (see the subtasks of CARGO-810 for details). The CARGO project does no longer use the "old-style" CARGO Maven2 repository, but rather uses Nexus.
- CARGO now uses the new Codehaus artifact release process and infrastructure
- CARGO artifacts are now signed (with GPG keys) in addition to the pre-existing MD5 and SHA1 checksums.
- In the future, this will give the opportunity to better manage our releases; taking advantage of the staging features of Nexus.
Enjoy this new release!
|