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 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
click in the status column to get release notes:
Version | Status | Comments |
|---|---|---|
| Released on 24/01/2012 |
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) |
|---|---|---|---|
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
| Resin 3.1.x |  1.2.0 | 1.2.0 | 1.2.0 |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
|
- 等级:
- 性别:
- 文章: 228
- 积分: 324
- 来自: 杭州
其实Maven就是一个插件平台+一个生命周期理论
我认为只要关注Maven的每一个人，都能根据Sonatype提供的文档达到足够入门的程度——不要过分追求技术化，比如动不动就自行开发插件啥的
我这个帖子的初衷还是讨论插件——Maven的两大核心之一。
当然了，如果大家有闲情，也可以讨论下这个生命周期理论下的相关心得
- unsid
- 等级:
- 性别:
- 文章: 232
- 积分: 100
- 来自: 北京
cobertura，生成测试覆盖率报告的
cargo，自动部署到远程服务器的
第一个有点意思，学习下
第二个感觉意义不大，真部署的话，还是手动部署的放心，而平时顶多就是集成调试下
比如你定时每天凌晨3点由hudson执行任务，从svn检出代码，编译，测试，生成报告，把报告发到程序员邮箱里，然后程序打包，将包部署到测试服务器，重启服务器这一串过程
第二天程序员一早上习惯性先首邮件，发现测试有错误修改代码，然后再点点测试服务器上的最新版本系统，没问题就开始今日的代码编写，如果没有cargo，靠maven deploy插件命令只能把包部署到私服上，不能到指定服务器的指定目录，整个链条到最后一步就断了。
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.