This page last changed on Oct 05, 2011 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 and Maven 2/Maven 3 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.1.3 |
|
Released on 05/10/2011 |
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 Maven2/Maven3 plugin). 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. Moreover, some containers are tested dialy on the Codehaus Cargo Continous Integration System; for these the container's page also shows which version is tested.
News
Dear CARGO enthusiasts
CARGO 1.1.3 is now ready. You're probably wondering what's in it for you; so here is a quick overview:
- The pingURL is no more ignored when using redeploy [CARGO-1036]
- All deployers now support the redeploy method (with and without monitor) [CARGO-1038]
- The JBoss container has gained in functionality and stability:
- JBoss 6.1.x support has been added [CARGO-1043]
- Corrected the capabilities of the JBoss 7.x remote container [CARGO-1044]
- Shared classpath does not cause java.net.MalformedURLException on Windows anymore [CARGO-1024]
- JBoss standalone local configuration creation now works even with deployables with certain names [CARGO-1037]
- Jetty-specific fixes and improvements:
- The latest version of Jetty, version 8, is now supported. [CARGO-1028]
- You can now provide your own Jetty context XML file [CARGO-1027] on Jetty 6.x, 7.x and 8.x
- The GlassFish container has been improved:
- Extra classpath support has been added [CARGO-1034]
- In addition, GlassFish containers now also support Datasources [CARGO-1035]
- That's not all: you can now use Existing Local Configuration for an installed GlassFish container [CARGO-1039]
- Finally, the GlassFish deployer has been improved to recognize failures correctly [CARGO-1032]
- The Tomcat container has two bugs corrected:
- A bug making the Tomcat container throw a ClassNotFoundException with default logging properties has been fixed [CARGO-1031]
- Deployment of a WAR with a subcontext works back again [CARGO-1041]
- In the containers' documentation's "properties" part, the "comments" column has been replaced with a link to Javadoc [CARGO-1029]
The full release notes can be found on: https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17504&styleName=Html&projectId=10730
Enjoy!
Hi CARGO enthusiasts
CARGO 1.1.2 is now ready, it comes with a number of new features and bug fixes.
On the new features and improvements side:
- CARGO now supports JBoss 7! (CARGO-1014)
- We have added new Maven2/Maven3 archetypes:
- Many CARGO components are now much easier to use:
- Configuration properties can now be set using Java system properties (-Dxxx=yyy) (CARGO-1007, CARGO-1009)
- The CARGO JBoss remote deployers are not needed to be in the classpath anymore, they're part of the JBoss container and are loaded dynamically (CARGO-1015)
- The cargo:run mojo is now much easier to use, and in many cases requires no plugin configuration at all:
- Configuration properties can now be set using Java system properties (-Dxxx=yyy) (CARGO-1007, CARGO-1009)
- New attributes: containerId and containerUrl (CARGO-970)
You can read our reworked Maven2/Maven3 plugin getting started guide, http://cargo.codehaus.org/Maven2+Plugin+Getting+Started and realize how easy it now is to use CARGO on any existing Maven2/Maven3 Java EE project; no configuration is required at all!
Of course, there are also some bug fixes:
- The Cargo Maven2/Maven3 deployer no more ignores deployables in the <configuration> element of the container (CARGO-1002)
- Adding a configuration file to a non-existing target directory does not result in FileNotFoundException anymore (CARGO-1004)
- The Maven2/Maven3 mojos now enable the logger in debug mode (CARGO-1010)
- The remote deployers now get their logger from the configuration (CARGO-1012)
- Some UberWar fixes:
- Dollar sign in value no more breaks NodeMerge strategy (CARGO-1016)
- Comma can now serve as a pattern end mark (CARGO-1017)
- Left side expression no more appears twice in the merged result (CARGO-1018)
- cargo:deploy on JBoss now works even when internet is unavailable (CARGO-1019)
- The JOnAS installed local deployer does not show an incorrect warning anymore (CARGO-1021)
Enjoy!
|