This page last changed on Jul 17, 2006 by vsiveton.
RSS
An RSS feed is available.
News
CARGO 1.0.6 is now available
Hello CARGO lovers
CARGO version 1.0.6 is now ready! As with all previous versions of CARGO, we have new features.
- CARGO can now deploy to remote GlassFish 3.x servers (see CARGO-828)! That support is based on the brand-new JSR88 Deployer.
- The abstract JSR88 deployer for CARGO, which closes one of the oldest JIRA tickets: CARGO-146. This will ease a lot the implementation of any JSR88-compliant container for CARGO.
Moreover, this version being a maintenance release, it also ships with the fix for the following issues:
- (CARGO-581) - A '/' in context path gets converted to %20
- (CARGO-875) - java.lang.StringIndexOutOfBoundsException: String index out of range: 5 at createJBossFilterChain(JBoss51xStandaloneLocalConfiguration.java:56)
- (CARGO-877) - Remote deployment on Jetty 7.1.6 using cargo-jetty-7-and-onwards-deployer fails
- (CARGO-879) - Cannot set JVM arguments in GlassFish
- (CARGO-880) - cargo-maven2-plugin - blank property value in container systemProperties causes NullPointerException
This version is also expected to be the last 1.0.x version of CARGO. Indeed, we will then be focusing our efforts on CARGO 1.1.0, which will have many changes and drop of dusty parts (such as the Maven1 plugin).
Enjoy!
CARGO 1.0.5 now available!
Hello, CARGO enthusiasts!
Just after the 1.0.4 release, I have sent the announcements I had been talking about, and we've had interesting reactions. Having taken the most important ones into account quikcly, we are happy to announce the immediate availability of CARGO 1.0.5. This time, CARGO did not change much and only includes bug fixes. Here is a short summary of the most interesting ones:
- [CARGO-863] - The maven2 plugin gives as extension ".bundle" to OSGi bundles (instead of .jar)
- [CARGO-865] - The remote cargo-jetty-deployer does not work with Jetty 7.2.0
- [CARGO-869] - Issues with the Maven archetypes
With this new version, the CARGO archetypes are compatible with Maven 2.x as well as Maven 3.x. Moreover, on the OSGi side, both GlassFish 3.x and OW2 JOnAS 5.x support bundle deployment.
CARGO users that prefer the Java API and/or the ANT tasks can download this new version via http://cargo.codehaus.org/Downloads
Those who use the Maven2 plugin simply have to change their plugin version in their POMs -the artifacts are already on the Maven2 central repository.
Enjoy this new release!
CARGO 1.0.4 released!
Hello, CARGO enthusiasts!
We are happy to announce the immediate availability of CARGO 1.0.4. This new version comes with 26 bug fixes, improvements and bug fixes, here is a short summary of the most interesting ones:
- The Apache Geronimo container is back again! Both versions 1.x (these are more than 4 years old, now!) and 2.x are supported, please see the documentation pages on http://cargo.codehaus.org/Geronimo+1.x and http://cargo.codehaus.org/Geronimo+2.x (I'll not list the JIRA tickets here, we have many of them!)
- Added support for the OSGi Bundle deployable type (CARGO-850 and some others). Currently, only the OW2 JOnAS 5.x container can handle bundles, hopefully that list should expand with the new versions of GlassFish and Geronimo.
- Made the new JBoss deployers, introduced in CARGO 1.0.3, work with big (tens of megabytes) files (CARGO-859); which actually is the filesize of real-life applications
- Various documentation updates (Documentation for pingTimeout, JBoss naming ports, missing property names, etc.)
- Made the FILE deployable actually support all types of files
- ... and more!
We have also finely tuned our release process, and CARGO 1.0.4 is the first CARGO version ever that has been tagged, staged, checked for quality and voted for during 72 hours before being released. Bravo, team! 
CARGO users that prefer the Java API and/or the ANT tasks can download this new version via http://cargo.codehaus.org/Downloads
Those who use the Maven2 plugin simply have to change their plugin version in their POMs -the artifacts are already on the Maven2 central repository.
Also, I will be sending nice e-mails on various application servers' mailing lists in order to introduce them CARGO. The current version can be seen on the "let's make some noise" page and all comments, corrections and ideas are most welcome.
Enjoy this new release!
CARGO 1.0.3 now available !
Hello CARGO enthusiasts,
6 weeks after CARGO 1.0.2, CARGO 1.0.3 has been released. That new version comes with 28 bug fixes and various improvements, in particular attention has been paid to remote containers:
- In the "CARGO samples", which run many tests on various containers and therefore guarantee a certain level of quality, we have re-enabled the testing of all Remote containers (CARGO-818).
- For a long (looooong) time, the CARGO JBoss remote deployer could not actually deploy to remote servers: it was expecting the file to deploy to be accessible by the JBoss server (which is possible using technologies like NFS, but that's not natural is it?). With CARGO 1.0.3, the JBoss remote deployer can upload and deploy your applications remotely on your JBoss server (versions 4.0.x, 4.2.x, 5.0.x, 5.1.x and 6.0.x). Read more here: http://cargo.codehaus.org/JBoss+Remote+Deployer, issue link here: CARGO-416
- On Jetty, the deployer helper application's path has been set to /cargo-jetty-deployer (it used to be the WAR's name, which contains version number and other non-determinictic data) (CARGO-820).
- On JOnAS, remote authentication issues have been corrected (CARGO-836) and the CARGO JOnAS deployer now supports the "development" mode (available since JOnAS 5) (CARGO-838).
- The Tomcat 7 remote deployer has been fixed (CARGO-817).
Moreover, CARGO 1.0.3 fixes other issues and adds interesting functionalities, of which:
- The Maven2 plugin now has a "skip" element for skipping CARGO (CARGO-481). That property can also be passed via a system environment variable.
- Fixed the MANIFEST of the WAR generated by CARGO uberwar (CARGO-727).
- Stopping the container does not longer corrupt the output file (CARGO-520).
Finally, we have also started a big move under the hood: move to Nexus (see the subtasks of CARGO-810 for details). The CARGO project does no longer use the "old-style" CARGO Maven2 repository, but rather uses Nexus.
- CARGO now uses the new Codehaus artifact release process and infrastructure
- CARGO artifacts are now signed (with GPG keys) in addition to the pre-existing MD5 and SHA1 checksums.
- In the future, this will give the opportunity to better manage our releases; taking advantage of the staging features of Nexus.
Enjoy this new release!
CARGO 1.0.2 released!
Hello CARGO enthusiasts
Since the release of CARGO 1.0.1 about a month ago, very important bugs have been fixed:
- The CARGO Maven2 was unusable for configurations with datasource configurations. We've also updated the Java API and ANT tasks' documentation accordingly.
- The CARGO ANT tasks required the CARGO uberjar to be in the ANT's $ANT_HOME/lib directory -which is not the way it was documented.
We have also made major improvements:
- To avoid these two major bugs from showing up again, we have started adding samples for the ANT tasks and Maven2 plugin; exactly the way all containers are tested using the Java API.
- All plugin dependencies now have their version numbers fixed. This enhances reproducibility and guarantees that CARGO can be built and will work, the exact same way, even years later.
- The Maven2 plugin now has a help goal.
- Tomcat 7.x has been added to the supported containers list, only weeks after its official release

- The Jetty 7.x remote deployer has been fixed.
This new version, CARGO 1.0.2, is now available for use.
Users of the Java API and ANT tasks can download this new version from the http://cargo.codehaus.org/Downloads page.
Those who prefer Maven2 only need to update their version number. In the case the new version is not on the Maven central yet, please also add the http://repository.codehaus.org/ repository is in your Maven2 repositories list.
Everyone enjoy this new version
|