This page last changed on Dec 03, 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.4 |
|
Released on 03/12/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
About 8 weeks have passed since the last CARGO release. During these weeks, some fixes and improvements have been implemented in CARGO, which include:
- General:
- Harmonized the behaviour when copying configuration files, now both <file> and <configfiles> can copy directories [CARGO-1045]
- Improved the module hierarchy and dependencies [CARGO-1011]
- This way, the CARGO Maven2 plugin doesn't use the uberjar anymore but rather the individual artifacts
- Cleaned notes about old CARGO versions from documentation [CARGO-997]
- Corrected Javadoc for MergeStrategy.inRight() [CARGO-1046]
- JBoss:
- JBoss 7.1.0 beta 1 is now supported [CARGO-1063]
- The JBoss 5.x and 6.x remote deployers now take into account username and password [CARGO-1058]
- JBoss 5.x, 5.1.x, 6.x, 6.1.x and 7.x local containers don't have cargo-specific XML files anymore [CARGO-839]
- Jetty:
- Fixed compatibility issues between the remote Jetty deployer and jetty-hightide (Jetty@Codehaus) [CARGO-983]
- Remote Jetty deployer now works with Jetty 8.x with the default OPTIONS [CARGO-1049]
- Fixed the default CARGO OPTIONS for the Jetty 8.x container [CARGO-1050]
- JOnAS:
- Remote deployer can now undeploy deployment plans on JOnAS 5.x [CARGO-1047]
- The standalone JOnAS container can now set any JOnAS configurator property [CARGO-1054]
- The modular ANT tasks are used when configuring the latest JOnAS 5.3 milestones [CARGO-1057]
- The JOnAS remote deployer has a new "ignore version" option [CARGO-1048]
- GlassFish:
- GlassFish2xAsAdmin now takes into account the timeout set in the container [CARGO-1055]
- Maven2/Maven3 plugin:
- Different executions can now have different configuration options [CARGO-1053]
You can access the full release notes by visiting https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17845&styleName=Html&projectId=10730
To use this new version:
- Users of the Java API and/or ANT tasks can download the CARGO uberjar and ANT tasks from the download page: http://cargo.codehaus.org/Downloads
- Maven2/Maven3 users simply need to change the plugin's <version> to 1.1.4, and Maven2/Maven3 will download the new version automatically.
Please share your good (and bad) findings on the user@cargo.codehaus.org mailing list.
Enjoy!
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!
|