This page last changed on Jul 17, 2006 by vsiveton.
RSS
An RSS feed is available.
News
CARGO 1.1.1 is here!
Hi CARGO enthusiasts;
CARGO 1.1.0 has been out for just over a month now, and we have had important bug fixes and improvements since. We therefore are very happy to announce CARGO 1.1.1.
Wonder what has changed? Here is a short list:
- A certain number of user inquiries made us realize that there has been a confusion around the wait parameter of the start ANT task and Maven goal of CARGO. Indeed, most other similar tools have a clearer separation:
- A "run" task/goal, which starts the container and waits until the user decides to stop it.
- A "start" task/goal, which starts the container and hands over to the next task/goal (run integration tests, for example).
- With version 1.1.1, CARGO also implements that behaviour.
- Of course the wait parameter remains available AND will remain so until CARGO version 1.3.0 at least.
- The various installers (introduced with CARGO 1.1.0) now have homogeneous parameters and default values.
- Fixes and improvements on various containers:
- The JBoss remote deployer now supports a wider range of configurations.
- Jetty 7.x and Tomcat 7.x remote deployers are now better documented to avoid some mistakes.
- Various improvements on the JOnAS containers:
- Added datasource support on JOnAS 4.x and 5.x.
- Added extra classpath support on JOnAS 5.x.
- Added undeploy and redeploy capabilities to the JOnAS 5.x local deployer.
- The webapp directory of Tomcat containers is now configurable.
And, the full changelog:
Fixed bugs:
- [CARGO-974] - default extraction dir for artifactInstaller is different from zipUrlInstaller
- [CARGO-978] - Broken link in site (Local Container)
- [CARGO-983] - cargo-jetty-7-and-onwards-deployer fails perform remote deploy on jetty-hightide (Jetty@Codehaus)
- [CARGO-984] - Remote redeploy does not work for Tomcat 7
- [CARGO-992] - Jonas 5.2: "mvn cargo:redeploy" don't work with the local deployer
Improvements and new features:
- [CARGO-973] - Add support for extractDir to artifactInstaller
- [CARGO-979] - Allow specifying the profile name when remotely deploying to a JBoss 5.1.X-server
- [CARGO-981] - Configuring Tomcat webapps Dir
- [CARGO-985] - Implement cargo:run
- [CARGO-989] - Implement run task
- [CARGO-994] - Add datasource support to JOnAS
- [CARGO-995] - Add extra classpath support to JOnAS 5.x
Other changes:
- [CARGO-987] - Deprecate cargo:start's -Dwait argument
- [CARGO-990] - Deprecate the ANT start task's wait argumen
Enjoy!
CARGO 1.1.0
Hi CARGO enthusiasts;
It has been more than usual since we did not come up with any new versions, and it is for a good reason: we have been working on CARGO's version 1.1.0. As usual, we have many bug fixes; but most notably we have very interesting new features.
Some of the interesting new features would perhaps be the following:
- The Maven2/Maven3 ZipUrlInstaller now reuses the proxy settings from Maven (CARGO-517)
- Container distributions can now be directory installed from a Maven2/Maven3 artifact definition (CARGO-449)
- ZipUrlInstaller now has different download and extraction directories (CARGO-907), and the default extraction directory for the Maven2/Maven3 plugin is the project's build directory (CARGO-908).
- This way, all containers can use the default directories of the ZipUrlInstaller (CARGO-895, CARGO-959 and others).
- The CARGO ANT tasks can now do remote deployment (CARGO-962)
- Deployable.pingUrl now supports authentication (CARGO-813)
- All deployment methods now accept a DeployableMonitor parameter (CARGO-414)
- The steps to follow in order to remotely debug a container is now documented (CARGO-447); you can check http://cargo.codehaus.org/Debugging for details
As for some of the improvements:
- Remote deployment on Jetty is now much faster (CARGO-884)
- Remote deployers can now change the WAR context (CARGO-331)
- The Container.stop method now waits for the whole server to stop (CARGO-918), which results in more stable tests if containers are started and stopped one after the other.
- Different timeouts can be defined when starting and stopping a container (CARGO-713)
- The JBoss remote deployer can now deploy to clusters (CARGO-899)
- Tomcat contexts' reloadable parameter can now be configured (CARGO-461)
- TomcatLocalInstalledLocalDeployer.shouldCopyWars() has been made configurable (CARGO-963)
- Container pages now include a link to the downloadable container used for tests (CARGO-313) as well as a link to the CI
- The Maven archetypes now use the failsafe plugin (CARGO-883)
And some fixes:
- CARGO now takes into account the encoding of your configuration and resource files (CARGO-900, CARGO-903 and CARGO-945)
- The GlassFish container's asadmin wrapper now correctly reports back errors (CARGO-914)
- The JBoss 4.x remote deployer now works with large files (CARGO-892)
- The Tomcat 7.x container now supports the latest Tomcat 7.x releases (CARGO-923)
- cargo:start does not fail with some versions of JBoss deployables when there's no internet connection (CARGO-956)
- The shared and extra classpath functionalities have been fixed (CARGO-928)
- Various fixes around Windows-configurations: CARGO-934, CARGO-893 and CARGO-939
And, finally, some major changes that you probably won't notice (but which are one of the reasons why we changed the version number to 1.1.0):
- CARGO can now be built with Maven3 (CARGO-789), which this also results in the removal of the Maven1 support (CARGO-793).
- All the code now uses Java 5 APIs and style (CARGO-656), moreover we have enforced the use of generics. We have also added checkstyle to all the code, including tests (CARGO-891).
- Java API users can now change the JVM launching method they like (CARGO-898), for example Eclipse instead of the default ANT.
... as well as some major changes you should take a note of:
- The default value for the wait parameter on the ANT and Maven2/Maven3 plugins is now false (CARGO-896)
- This means you will need to run mvn cargo:start -Dwait=true when you want to run manual tests.
- This change in fact renders the creation of automated integration tests easier.
- ZipUrlInstaller now has different download and extraction directories (CARGO-907), which makes the installDir property obsolete: it is replaced by downloadDir and extractDir, the old property set them both but will probably removed in CARGO 1.2.0.
- TomcatPropertySet.MANAGER_URL has been deprecated in favor of RemotePropertySet.URI (CARGO-964).
- TomcatLocalInstalledLocalDeployer.shouldCopyWars() is set to true by default (used to be false) (CARGO-963)
- Deployable.isExpanded() and Deployable.isExpanded*() have been consolidated, obsoleting the Deployable.isExpanded*() methods (CARGO-902).
- All API methods for copying configuration and resource files that specify no encoding are deprecated (CARGO-900, CARGO-903 and CARGO-945)
- AbstractCopyingInstalledLocalDeployer.setShouldDeployExpanded*s() and AbstractCopyingInstalledLocalDeployer.setShouldDeployExpanded() have been consolidated, obsoleting the AbstractCopyingInstalledLocalDeployer.setShouldDeployExpanded*() methods.
For a full list, you can always check the release notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10730&version=16436 -we have more than 80 changes!
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.0, 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!
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!
|