Blog from Nov 11, 2012

CARGO 1.3.1 is available

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: