Cargo : News

RSS


An RSS feed is available.

News


Dear CARGO enthusiasts

We are happy to announce the immediate availability of CARGO 1.4.2. This version brings the below bug fixes, enhancements and new features:

To upgrade to this new version:

Enjoy!
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:
  • Containers - Resin:
  • Daemon:
    • [CARGO-1188] - Add -nologging option to disable logging for standalone daemon war
    • [CARGO-1180] - Add support for continuously viewing logs
    • [CARGO-1181] - Add support for restarting offline containers
    • [CARGO-1182 and CARGO-1184] - Change the Daemon properties in the Maven2/Maven3 plugin configuration to have a proper configuration
    • [CARGO-1187] - Daemon start/stop mojos does not have dependency resolution
    • [CARGO-1185] - Add support for extra and shared classpaths
    • [CARGO-1186] - Add support for adding classpath locations at verbatim
    • [CARGO-1183] - Fix integration test Cargo Daemon Integration Tests - Browser
    • [CARGO-1192] - Daemon doesn't work if the Maven2/Maven3 client and Daemon server run different OSes
  • Extensions - ANT tasks:
    • [CARGO-991] - Remove the start task's wait argument
  • Extensions - Maven2/Maven3 plugin:
    • [CARGO-1116] - Remove the deprecated <deployable> elements under <deployer> and <configuration>
    • [CARGO-967] - Use the tested container downloadable as the default for the ZipUrlInstaller
    • [CARGO-986] - Remove cargo:start's wait argument

To upgrade to this new version:

IMPORTANT: Users of the ANT tasks and Maven2/Maven3 plugin should consider CARGO-991 and CARGO-986, i.e. the removal of the long-deprecated wait argument. If you want the container to start and keep on running, please use run instead of start.
IMPORTANT: Users of the Maven2/Maven3 plugin should consider CARGO-1116 when upgrading, i.e. the removal of the deprecated <deployable> elements under <deployer> and <configuration>. All <deployable> elements are now under the main <configuration> element.

Enjoy!
CARGO 1.3.3 is here!

Dear CARGO enthusiasts

CARGO 1.3.3 is here! This new version features the below fixes and improvements:

To upgrade to this new version:

Enjoy!

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:
  • Containers - Tomcat:
    • AbstractTomcatManagerDeployer now throws an exception if the undeploy operation is called for a deployable which is not deployed (CARGO-1167)
    • Default user role now work with management application in Tomcat 7.x (CARGO-1165)
    • TomcatManagerInstalledLocalDeployer now has an implementation for Tomcat 7.x (CARGO-1166)
  • CARGO Daemon:
    • The Daemon WAR now works properly with various servers, Jetty, Glassfish and Tomcat have been tested (CARGO-1161)
  • Maven2/Maven3 plugin:
    • The deployer pingTimeout logs are now displayed properly (CARGO-1168)
    • The behaviour when a non-absolute path is specified in plugin / task configuration has been improved (CARGO-1162)

To upgrade to this new version:

Enjoy!

Dear CARGO enthusiasts

A few weeks after version 1.3.0, CARGO 1.3.1 is now ready -with the fixes for the below issues:

  • JBoss
    • JBoss 7.x and 7.1.x local deployer does not take into account WAR context if a shared or extra classpath needs to be set [CARGO-1156]
    • JBoss 7.x or 7.1.x datasource classes cannot come from shared classpath [CARGO-1157]
  • Jetty:
    • Upgrade the Jetty 9.x container to support Jetty 9.0.0.M1 and 9.0.0.M2 [CARGO-1152]
  • WebSphere
    • WebSphere deployment fails for WARs with <display-name> set [CARGO-1153]
  • Daemon
    • CARGO daemon does not work with Jetty [CARGO-1155]
    • Daemon Java client cannot start container when ZipUrlInstaller is set [CARGO-1158]
    • Daemon Java client throws NullPointerException if no deployables have been set [CARGO-1159]
    • NullPointerException on daemon webapp in some situation [CARGO-1154]

It also comes with one small improvement: the directory where to deploy web archives for Tomcat installed containers is now taken from server.xml file [CARGO-455]. Moreover, we have added some automated tests for the Cargo Daemon [CARGO-1150].

To upgrade to this new version:

Enjoy!