Home Page Cargo : Home

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.
  • A Java API to (remotely or locally) deploy modules into these containers, be it a server alone, a farm or a cluster.
  • A Java API to parse/create/merge J2EE modules.
  • ANT tasks wrapping the Java API for configuring, starting, stopping and deploying applications to all supported containers.
  • A Web interface that wraps the Java API that can be used to configure, start and stop all containers supported by Cargo remotely and at any time.
  • Maven2/Maven3 plugins wrapping the Java API for configuring, starting, stopping and deploying applications to all supported containers as well as parsing, creating and merging J2EE modules.

These tools and APIs can be used in a standalone fashion or via various IDEs.

Usage

Cargo is often used to deploy applications to containers from test APIs (such as JUnit), ANT or Maven builds. Cargo can install the container and dependencies needed for your deployment as well. Please find below the links to our Quick Start guides:

Development Status

Current Versions

You can click on the version number to access the Downloads page and in the status column to get release notes:

Version

Status

Comments

1.4.0

(tick)

Released on 16/04/2013

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.

Container

Java API (version)

Ant tasks (version)

Maven 2 plugin (version)

Geronimo 1.x

(tick)
0.8

(tick)
0.8

(tick)
0.8

Geronimo 2.x

(tick)
1.0.4

(tick)
1.0.4

(tick)
1.0.4

Geronimo 3.x(tick)
1.2.4
(tick)
1.2.4
(tick)
1.2.4

Glassfish 2.x

(tick)
1.0.1

(tick)
1.0.1

(tick)
1.0.1

Glassfish 3.x

(tick)
1.0.1

(tick)
1.0.1

(tick)
1.0.1

Glassfish 4.x(tick)
1.4.0
(tick)
1.4.0
(tick)
1.4.0

JBoss 3.x

(tick)
0.7

(tick)
0.7

(tick)
0.7

JBoss 4.x

(tick)
0.7

(tick)
0.7

(tick)
0.7

JBoss 4.2.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

JBoss 5.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

JBoss 5.1.x

(tick)
1.0.1

(tick)
1.0.1

(tick)
1.0.1

JBoss 6.x

(tick)
1.0.1

(tick)
1.0.1

(tick)
1.0.1

JBoss 6.1.x

(tick)
1.1.3

(tick)
1.1.3

(tick)
1.1.3

JBoss 7.x

(tick)
1.1.2

(tick)
1.1.2

(tick)
1.1.2

JBoss 7.1.x

(tick)
1.1.4

(tick)
1.1.4

(tick)
1.1.4

Jetty 4.x

(tick)
0.1

(tick)
1.0

(tick)
0.2

Jetty 5.x

(tick)
0.8

(tick)
1.0

(tick)
0.2

Jetty 6.x

(tick)
0.8

(tick)
1.0

(tick)
0.2

Jetty 7.x

(tick)
1.0.1

(tick)
1.0.1

(tick)
1.0.1

Jetty 8.x

(tick)
1.1.3

(tick)
1.1.3

(tick)
1.1.3

Jetty 9.x

(tick)
1.3.0

(tick)
1.3.0

(tick)
1.3.0

jo! 1.x

(tick)
0.5

(tick)
0.5

(tick)
0.1

JOnAS 4.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

JOnAS 5.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

JRun 4.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

Oc4J 9.x

(tick)
0.3

(tick)
0.3

(tick)
0.3

Oc4j 10.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

Resin 2.x

(tick)
0.1

(tick)
0.1

(tick)
0.1

Resin 3.x

(tick)
0.1

(tick)
0.1

(tick)
0.1

Resin 3.1.x(tick)
1.2.0
(tick)
1.2.0
(tick)
1.2.0
Resin 4.x(tick)
1.4.0
(tick)
1.4.0
(tick)
1.4.0

Tomcat 4.x

(tick)
0.1

(tick)
0.1

(tick)
0.1

Tomcat 5.x

(tick)
0.1

(tick)
0.1

(tick)
0.1

Tomcat 6.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

Tomcat 7.x

(tick)
1.0.2

(tick)
1.0.2

(tick)
1.0.2

WebLogic 8.x

(tick)
0.3

(tick)
0.3

(tick)
0.1

WebLogic 9.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

WebLogic 10.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

WebLogic 10.3.x

(tick)
1.0

(tick)
1.0

(tick)
1.0

WebLogic 12.x(tick)
1.2.4
(tick)
1.2.4
(tick)
1.2.4
WebSphere 8.5.x(tick)
1.3.0
(tick)
1.3.0
(tick)
1.3.0


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

CARGO 1.4.0 is here!
Dear CARGO enthusiasts Almost two months after CARGO 1.3.3, we've gone a long way through CARGO 1.4.0. Major enhancements, changes and bug fixes include: Core: [CARGO-365] - CARGO should check status of application server before attempting to start container [CARGO-1068] - Add support for port offset for containers Containers - Glassfish: [CARGO-1189] - Glassfish jvm-options should not be quoted [CARGO-1190] - Glassfish <systemProperties> should be XML-encoded when added to domain.</systemProperties>…
CARGO 1.3.3 is here!
Dear CARGO enthusiasts CARGO 1.3.3 is here! This new version features the below fixes and improvements: Containers - General The configuration files option now overrides all existing files (CARGO-1176) Containers - Glassfish Glassfish deployment does not fail anymore on Windows when context is / (CARGO-1179) Containers - JBoss Support for the append parameter has been added to the JBoss logger configuration (CARGO-825) JBoss 7.x and 7.1.x now support JBossPropertySet.…
Dear CARGO enthusiasts CARGO's first version in 2013, version 1.3.2, is now ready! This new version fixes the below issues: Containers - JBoss: JBoss 7.x and JBoss 7.1.x containers now support ServletPropertySet.USERS (CARGO-1163) The JBoss 7.x and 7.1.x Remote Deployer now handles disconnections properly,…

Attachments:

architecture.jpg (image/jpeg)
architecture.jpg (image/jpeg)
access-layers.jpg (image/jpeg)
access-layers.jpg (image/jpeg)
access-layers.jpg (image/jpeg)
print.gif (image/gif)