Codehaus Cargo : News

RSS


An RSS feed is available.

News


Dear Codehaus Cargo enthusiasts

Only a few days after the release of Codehaus Cargo 1.9.0, we are happy to release its first bug fix version 1.9.1. This version comes with the below bug fixes and improvements:

  • Build process

  • Containers - JBoss

    • [CARGO-1546] - JBoss 5.x to 7.1.x remote deployers are broken

  • Containers - Payara

    • [CARGO-1547] - After upgrade to cargo-maven3-plugin:1.9.0 cannot start Payara

  • Containers - WebSphere

  • Extensions - Maven 3 plugin

    • [CARGO-1549] - Align and centalize dependency and plugin versions used in Maven archetypes and samples

To try out this latest version:

Enjoy!

Dear Codehaus Cargo enthusiasts

As announced two days ago, Codehaus Cargo 1.9.0 is now ready, and features one and only change:

  • Extensions - Maven 3 plugin

    • [CARGO-1544] - Upgrade the Codehaus Cargo Maven plugin to Maven 3
      Note: This implies that we don’t have a Maven 2 plugin anymore, and only a Maven 3 plugin.

Though this change is quite nicely in line with the Maven 2.x end of life from November 2009, it does imply slightly some more work from your side than usual.

To try out this latest version:

Enjoy!

Dear Codehaus Cargo enthusiasts

A couple weeks after our last release, please give a warm welcome to Codehaus Cargo 1.8.5! This new version has many “under the hood” changes (in particular, around the dependency versions we use) and features the below improvements:

  • Extensions - Maven 2 / Maven 3 plugin

    • [CARGO-1543] - Added tomcat-dbcp to the embedded Tomcat container classpath

    • [CARGO-1501] - Mojos that are thread safe should be marked with the appropriate annotation so that maven can run parallel builds
      Note: Though Codehaus Cargo itself is thread safe, we would recommend to use this feature with great care: you are most likely using Codehaus Cargo to perform integration tests on containers, you might run into port number clashes when executing the containers in parallel if you’re not careful.

This will also be our last 1.8.x version, the reason being that the current Maven 2 / Maven 3 plugin (which behind the scenes is a Maven 2 plugin which Maven 3 can also use) will be removed and become a Maven 3 only plugin. This is quite nicely in line with the Maven 2.x end of life from November 2009.

To try out this latest version:

Enjoy!

Dear Codehaus Cargo enthusiasts

We are hoping you had a nice start to 2021!

On this second day of 2021 we are happy to announce Codehaus Cargo version 1.8.4. This new version comes with a bug fix, and a full support for Jakarta EE:

  • General

    • [CARGO-1514] - Add the Jakarta EE converter to samples of affected containers
      To achieve this, we actually integrated the Jakarta EE migrator into our build (more precisely, per-container testing) process and it is quite a promising piece of software! We hence also adapted, for the supporting containers, the deployment of javax.jms and javax.mail to support their Jakarta EE counterparts and to intelligently mirror these when needed. For those of you who don’t yet have a goal for 2021, Jakarta EE migration can definitely be a good one (wink)

  • Containers - GlassFish

  • Containers - Tomcat and TomEE

To try out this latest version:

Enjoy!

Dear Codehaus Cargo enthusiasts

As most of us are getting ready to say goodbye to 2020, we are happy to announce our last Codehaus Cargo release for 2020, version 1.8.3. This new version comes with many improvements and some bug fixes:

  • General

    • [CARGO-1535] - AbstractInstalledLocalContainer#addMemoryArguments is inconsistent with the boolean server parameter from AbstractInstalledLocalContainer#createJvmLauncher

  • Containers - Jetty

    • [CARGO-1536] - Add support for Jetty 10.x.
      Jetty 10 has changed the “inner workings” of certain portions of Jetty, we hence have a new version of the Jetty Remote Deployer WAR only for Jetty 10.

    • [CARGO-1537] - Add support for Jetty 11.x.
      Jetty 11 marks the switch from to Jakarta EE, which implies that the primary package for all implemented APIs has changed from javax. to jakarta., we hence have a new version of the Jetty Remote Deployer WAR for Jetty 11 (onwards).

  • Containers - GlassFish

  • Containers - Tomcat

    • [CARGO-1534] - Tomcat 8.x and onwards embedded local containers show a No global web.xml found error when starting

  • Containers - WildFly

  • Extensions - Maven 2 / Maven 3 plugin

    • [CARGO-1533] - Maven plug in ignores/erases proxy settings specified as system properties on the command line

To try out this latest version:

And, of course, with this we also wish you a great start to the new year - Stay safe!