News

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:
  
  • JBoss 7.x and JBoss 7.1.x containers now support ServletPropertySet.USERS (CARGO-1163)
  • The JBoss 7.x and 7.1.x Remote Deployer now handles disconnections properly, avoiding JBREM000200 ERROR logs on the JBoss console (CARGO-1164)
• 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:

• Users of the Maven2/Maven3 plugin simply need to use the CARGO plugin version 1.3.2.
• Users of the Java API can download the new Uberjar from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.3.2/cargo-core-uberjar-1.3.2.jar
• Similarly, users of the ANT tasks can download the new ANT tasks from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-ant/1.3.2/cargo-ant-1.3.2.jar
• Finally, the ones who want to use the Cargo Daemon can download the webapp from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.3.2/cargo-daemon-webapp-1.3.2.war

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:

• Users of the Maven2/Maven3 plugin simply need to use the CARGO plugin version 1.3.1.
• Users of the Java API can download the new Uberjar from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.3.1/cargo-core-uberjar-1.3.1.jar
• Similarly, users of the ANT tasks can download the new ANT tasks from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-ant/1.3.1/cargo-ant-1.3.1.jar
• Finally, the ones who want to use the Cargo Daemon can download the webapp from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.3.1/cargo-daemon-webapp-1.3.1.war

Enjoy!

Dear CARGO enthusiasts

Our next big release of CARGO, version 1.3.0, is now available! It comes with a lot of very attractive new features:

• The newest and latest Jetty 9.x is supported [CARGO-1147]
• IBM WebSphere 8.5.x container has been added -making another very old CARGO ticket get solved! [CARGO-147]
• We have introduced a new feature, the Cargo Daemon: this is a Web-based application that uses the Cargo API to configure, start and stop containers on a remote machine. The daemon is meant to be listening 24/7, to allow users to deploy new containers and web applications at their command. It can be accessed using a browser-based UI, via Java API or Maven2 plugin. [CARGO-1148]
• Local and embedded deployer support has been added to the ANT plugin [CARGO-1144]

The Apache Geronimo container has been improved a lot as well:

• Bundle support has been added to Geronimo 3.x [CARGO-1143]
• Extra classpath can now be set on Geronimo 2.x and 3.x [CARGO-1145]
• It is now possible to define datasources on Geronimo 2.x and 3.x [CARGO-1146]

We have also fixed some JBoss issues (all of them on JBoss 7.x and 7.1.x):

• Non-default deployment directory is now supported [CARGO-1141]
• GeneralPropertySet.RUNTIME_ARGS is now set at the correct place [CARGO-1139]
• Extra and shared classpath is now fully supported [CARGO-1149]

As for the other fixes and improvements:

• Direct configuration of SSL/TLS connector options for Tomcat 5.x, 6.x, and 7.x stand alone local configurations is allowed [CARGO-1135]
• OC4J's MIME types now has text/css [CARGO-281]
• Property injection from Maven settings.xml has been fixed [CARGO-1136]
• Non 200 HTTP status codes are accepted by the deployment's ping component [CARGO-1118]
• Shared classpath for WARs are now supported on Jetty [CARGO-948]

To try this new version:

• Users of the Maven2/Maven3 plugin simply need to use the CARGO plugin version 1.3.0.
• Users of the Java API can download the new Uberjar from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.3.0/cargo-core-uberjar-1.3.0.jar
• Similarly, users of the ANT tasks can download the new ANT tasks from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-ant/1.3.0/cargo-ant-1.3.0.jar
• Finally, the ones who want to use the Cargo Daemon can download the webapp from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.3.0/cargo-daemon-webapp-1.3.0.war

Enjoy!