Release note content:
Here are the highlights of Cargo 0.8:
- Added support for Jetty 5.x and 6.x
- Added Geronimo support
- Added JMX hot deployer for JBoss 4.x
- Firmed up the Cargo APIs and several usability improvements
- Added notion of Embedded containers
The full list of all issues fixed and features implemented is available below.
Please note that version 0.8 has broken several APIs as explained below in the migration guide. This is one of the last 0.X version before the 1.0 release and we took the opportunity to fix the API now rather than to go through a lengthy and difficult deprecation strategy (which we'll use once 1.0 is out). We apologize to all our early users for this.
Migration guide from 0.7 to 0.8
This sections lists the principal differences in Cargo 0.8 which you may require you to modify the way you use Cargo. The full list of changes is shown below in the Clirr section.
For extension users
localcontainer type replaced by
For example if you were before using the m2 plugin with:
You'll now have to use a type of
installed for Installed Container and a type of
embedded for Embedded Container. The same applies for the Ant and Maven1 extensions. If no type is specified it defaults to an Installed Container.
dirattribute (for the Ant task),
....config.dirproperty (for the Maven 1 plugin)
direlement (for the Maven 2 plugin) by
hometo be aligned with the Java API.
- There's now a
waitattribute for the Cago Ant task to tell Ant to wait after the container is started. The Maven1 plugin has also been modified to use a new
cargo.container.waitproperty to do the same.
For users of the Cargo Java API
- Renamed logging interfaces and
get/setMonitor()have been replaced by
get/setLogger(). This is to prevent a clash with the notion of Monitor which we're reserving for monitoring container and deployables.
LocalContainer.setHome(String)API. Please always use the
- Added new
org.codehaus.cargo.container.InstalledLocalContainerclasses to differentiate Installed Container from Embedded Container.
ConfigurationFactory.createContainer(String, Configuration)signature. You need to use the signature with the
ContainerTypeparameter (it was previously defaulting to a local container).
- Renamed all container implementation from
*InstalledLocalContainer, except for Jetty 4.x which name has not changed.
This is the report generated by Clirr on the different Cargo APIs:
- Core Container API
- Core Generic API
- Core Module API
- Core Util API
- JBoss API
- Jetty API
- Jo API
- Orion API
- Resin API
- Tomcat API
- WebLogic API
- Ant API
- Maven2 API
Core Container API
Core Generic API
Core Module API
Core Util API