Blog

Blog

Dear CARGO users

CARGO 1.4.8 is available - and we promise, this is no April fool! This version fixes the below issues and comes with the below improvements:

  • General:
    • [CARGO-341] - FileHandler should support an operation that explodes a war
    • [CARGO-717] - Support binding to all ip addresses
    • [CARGO-1260] - Include cause exception in log output when deployment fails
  • Containers - Glassfish:
    • [CARGO-1246] - Add cargo.servlet.users support to Glassfish 4.x
    • [CARGO-1258] - Add support for cargo.datasource.properties to the GlassFish3xInstalledLocalDeployer
  • Containers - JBoss:
    • [CARGO-1265] - For ExistingInstalledLocalContainercargo.jboss.management-native.port value incorrectly defaults to 9990 (the http management port)
  • Daemon:
    • [CARGO-1262] - Daemon client API throws exception for start command if only handleId is defined
    • [CARGO-1266] - Fix progressive log viewing
    • [CARGO-1267] - Webcontainer sockets can possibly still be open after native process kill
  • ANT:
    • [CARGO-418] - Allow <cargo> task to load configuration from external property file
    • [CARGO-1264] - Support deployable pingURL/pingTimeout for ANT task
  • Maven2/Maven3 plugin:
    • [CARGO-1263] - The cargo:run goal in combination with starting a debugger fails to shut down cleanly

To try it out:

Enjoy this new version of CARGO!

Dear CARGO users

CARGO's first release for 2014, version 1.4.7, is now available. This version fixes the below issues and comes with the below improvements:

  • General fixes
    • [CARGO-1248] - The port offset should not be applied more than once in the same local configuration
  • Glassfish
    • [CARGO-1255] - Unable to start Glassfish in debug mode
    • [CARGO-1245] - Allow passing extra parameters for Glassfish deployment
    • [CARGO-1253] - Provide support for creating JMS resource on Glassfish 3.x and 4.x
    • [CARGO-1254] - Add support for javax.mail.Session resource to Glassfish 3.x and 4.x
  • JBoss
    • Important change: [CARGO-1249] - The properties JBossPropertySet.JBOSS_USER and JBossPropertySet.JBOSS_PASSWORD have been replaced with the equivalents from RemotePropertySet
    • [CARGO-1247] - The stop implementaion of local JBoss containers should consider username and password
    • [CARGO-1257] - Adding JBDC driver to EAR classpath fails with java.lang.NegativeArraySizeException on JBoss 7.x and onwards
  • Jetty
    • [CARGO-1252] - Error java.io.IOException: modules/npn/npn-1.7.0_02.mod or similar when starting Jetty 9.1.1
  • WebLogic
    • [CARGO-1250] - Weblogic 12.1.2.0 does not find config.xml

To try it out:

Enjoy this new version of CARGO!

CARGO 1.4.6 is here

Dear CARGO users

CARGO's Christmas 2013 release, version 1.4.6, is now live. This version fixes the below issues and comes with the below improvements:

To try it out:

Please enjoy your celebrations, and also this new version of CARGO.

CARGO 1.4.5 is here!

Dear CARGO enthusiasts

We are happy to announce the immediate availability of CARGO's new bug fix release, version 1.4.5. This version brings the below bug fixes and small improvements:
  • New features / updates:
    • Add compatibility with JOnAS 5.3.x [CARGO-1226]
    • Add property to disable the default Glassfish datasource [CARGO-1223]
    • Remove the ${versionId} from the default WAR context / EAR names of Deployables [CARGO-1225]
  • Bug fixes:
    • Issue when deploying applications on WebSphere with regards to the display-name of web.xml for WARs inside EARs [CARGO-1228]
    • JBoss7xInstalledLocalContainer unable to stop container running on hostname other than localhost [CARGO-1222]
    • JBoss7xInstalledLocalContainer should allow override of -mp param via system property [CARGO-1227]
    • Not all JVM options are supported for Glassfish [CARGO-1224]
    • NullPointerException in when adding classpath entry for ResinRun [CARGO-1230]

To upgrade to this new version:

Enjoy!

Dear CARGO enthusiasts

We are happy to announce the immediate availability of CARGO 1.4.4. This version brings the below bug fixes, enhancements and new features:
  • Common:
  • Containers:
    • Reorganized the management port properties for JBoss 7.x and onwards (including WildFly) [CARGO-1216].
    • Added support for Tomcat 8.x [CARGO-1217].
    • Added support for Tomcat's useHttpOnly property [CARGO-1212].
    • Allow users to override java.util.logging.config.file and java.util.logging.manager when using local Tomcat containers [CARGO-1220].
  • Daemon:
    • The management of start / stop requests have been rethought and reorganized. This in particular enhances the handling of concurrent requests with the same handleid [CARGO-1213].
    • Allow viewing of both container log output and CARGO log output [CARGO-1214].
    • Show Daemon version on website [CARGO-1215].

To upgrade to this new version:

Enjoy!

CARGO 1.4.3 is here!
Dear CARGO enthusiasts

We are happy to announce the immediate availability of CARGO 1.4.3. This version brings the below bug fixes, enhancements and new features:
  • Common:
    • The property cargo.process.spawn is now working back again [CARGO-1206]
  • Containers:
    • Support for JBoss 7.2.x (also known as EAP 6.1.0) has been added [CARGO-1208]
    • Jetty containers now also have Packager support [CARGO-1210]
  • Daemon:
    • Daemon credentials (HTTP Basic) can now be provided to the Maven plugin configuration [CARGO-1202]
    • The Daemon can now deploy the same deployable twice (with different contexts, obviously) [CARGO-1201]
    • Issues starting GlassFish (and also some other containers) with the Daemon have been fixed [CARGO-1211]
    • In the case the launched Java process doesn't stop properly, the Daemon will now kill it [CARGO-1203] [CARGO-1204] [CARGO-1205]
  • XML merger:
    • Merging listeners when the root (<web-app>) of web.xml contains the xmlns attribute now works well [CARGO-1209]

To upgrade to this new version:

Enjoy!

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!

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:

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:

Enjoy!

Dear CARGO users

After about one month from the last release, CARGO 1.2.4 is now here! It comes with three important new features:

  • WebLogic 12.x support has been added (CARGO-1132)
  • Geronimo 3.x is now supported (CARGO-1126)
  • Geronimo 2.x and 3.x containers are able of working with existing standalone configurations (CARGO-1127)
  • Jetty 8.x now supports ServletContainerInitializers (CARGO-1133)

Apart form that, this versions also comes with some bug fixes:

  • Exception messages when the user defines no ContainerId but uses a ZipUrlInstaller or ArtifactInstaller have been improved (CARGO-1128)
  • Exception messages when one attempts to use a local deployer for a non-existing directory have been improved (CARGO-1131)
  • Cargo plugin does not expect to be executed from inside .jar anymore (CARGO-1129)

Full release notes are accessible on https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18669&styleName=Html&projectId=10730

To try this new version:

Enjoy!

Dear CARGO enthousists.

After about two months from the last release, CARGO 1.2.3 is now ready.

This new version comes with only one new feature, support for setting JBoss AJP ports (CARGO-1112).

Apart from that, this version fixes the below bugs:

  • ANT tasks and Maven2/Maven3 plugin:
    • The cargo:run MOJO and run ANT task now try to stop the container (via shutdown hook) when CTRL + C is pressed (CARGO-1124)
  • Maven2/Maven3 plugin fixes:
    • cargo:run now deploys all WARs; as the <deployables> element has been centralized (CARGO-1114)
    • The intreaction between the CARGO Maven2/Maven3 plugin and Maven proxy settings have been reviewed to function in an homogeneous manner (CARGO-1119 and CARGO-1121)
  • General fixes:
    • The configuration of <cargo.servlet.users> does not require a role anymore (CARGO-526)
  • Container-specific fixes:
    • Jetty 7.x and 8.x Remote Deployment now works properly if Jetty-JNDI is active (CARGO-1122 and CARGO-1123)
    • Jetty installed local deployer has been fixed to be able of deploying sub-contexts (CARGO-1125)
    • jboss.server.lib.url is now correctly handled (CARGO-1110)
    • WARs can now be deployed on JBoss 7.x and 7.1.x containers' root context (CARGO-1090)
    • JBoss 7.x and 7.1.x contains' bind address can now be set to 0.0.0.0 (CARGO-1111)
    • Tomcat NIO connectors now work properly with CARGO (CARGO-1115)

The full release notes are accessible on https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18524&styleName=Html&projectId=10730

To try this new version:

We have another amazing news to share: over the last 12 months, overall download count of the CARGO components have gone up 60%. See below, for example, for the Maven2/Maven3 plıugin:

We thank you again for your continuing interest.

Enjoy!

CARGO 1.2.2 available!

Dear CARGO enthusiasts

After about 7 weeks after the last release, I decided we have enough changes and fixed bugs in order to go ahead with CARGO 1.2.2. As for what's new, the list is this time small (12 entries):

Improvements and new features (5)

    • Jetty containers now support datasources (CARGO-1107)
    • Jetty 7.x standalone local container is now the default container for the CARGO Maven2/Maven3 plugin (CARGO-1106) and downloads its container via the artifactInstaller
    • The usage of an external jetty-env.xml file has finally been documented (CARGO-861)
    • The XML/properties replacement engine can now WARN when a replacement is not possible (instead of failing) (CARGO-1099)
    • Deployers (and mostly undeployers) can now intelligently ignore failures when deploy/undeploy fails (for example, if the application is not deployed but one attempts to undeploy it) (CARGO-1100)

Bug fixes (7)

    • Proxies that would be previously set by Maven are not used during deployment anymore (CARGO-1042)
    • Module names in JBoss do not contain any periods anymore -allowing the deployment of datasources via Maven2/Maven3 plugin (CARGO-1091)
    • Logging level is now interpreted properly for containers that output their messages on stderr (CARGO-1095)
    • Jetty can deploy to root (/) context (CARGO-1103)
    • cargo.jboss.invoker.pool.port configuration property works properly for JBoss 5+ (CARGO-1104)
    • Merging of XML files doesn't throw a ConcurrentModificationException anymore (CARGO-1105)
    • JVM properties on Glassfish now work (CARGO-1108)

In addition to these, we have done various changes in the documentation as well as the Maven archetypes. For example, a profile for JBoss 7.1.x has been added to all archetypes and is configured with an artifactInstaller.

The full release notes can be found on https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18384&styleName=Html&projectId=10730

To use this new version:

  • Users of the Java API and/or the ANT tasks can download the required components (be it the uberjar, ANT tasks and others) via the CARGO Downloads page.
  • Users of the Maven2/Maven3 plugin simply need to change their plugin version to 1.2.2.

Please provide your feedback to the user@cargo.codehaus.org mailing list.

Enjoy!