Independent extensions:

RSS Feeds


Pages and Blog posts
Mailing list

RSS


An RSS feed is available.

News


Dear Codehaus Cargo enthusiasts

We are happy to announce Codehaus Cargo 1.9.7, which includes the below two bug fixes and one improvement:

  • Containers - Tomcat

  • Containers - WildFly

    • [CARGO-1569] - The WildFly Remote Deployer doesn’t handle the Digest authentication properly

  • Various containers and Cargo Daemon:

    • [CARGO-1570] - Use HttpRequest, HttpFileRequest and HttpFormRequest instead of individual HttpURLConnection instantiations

That last item in the list has been triggered by the issue observed with the WildFly Remote Deployer, and now (almost) all Codehaus Cargo components which connect to HTTP(S) resources (be it the Jetty Remote Deployer, the various clients for Cargo Daemon, etc.) use these common classes. That means they all de facto also support Digest authentication and other features.

To upgrade to this latest version:

Enjoy!

Dear Codehaus Cargo enthusiasts

We are happy to announce Codehaus Cargo 1.9.6, which includes two improvements:

  • Core

    • [CARGO-1566] - When checking a port being closed, try to open the port instead of trying to connecting to it

  • Containers - WildFly

To upgrade to this latest version:

Enjoy!

Dear Codehaus Cargo enthusiasts

We are happy to announce Codehaus Cargo 1.9.5, which includes two bug fixes:

  • Containers - Tomcat

    • [CARGO-1563] redeploy fails when <properties> element has <context>ROOT</context>

    • [CARGO-1564] JOTM UserTransactionFactory is always added to my Tomcat server.xml
      This bug is an interesting one: the JOTM UserTransactionFactory, though seemingly “never” used, has been added to the Tomcat server.xml since the initial commit of the Tomcat 5.x standalone configuration back in 2007, where the only statement explaining it was we will likely need a transaction factory too, though our many integration tests show that we actually do not.

This version also comes with some behind the scenes improvements so Codehaus Cargo can be built on JDK 16, though one will need to follow the instructions for building on non JDK 11 versions to fully achieve a build (and a release is not possible on any other JDK than JDK 11). These should, nevertheless, be a non-impact for you as a user and you can use any Java environment version 8 or above.

To upgrade to this latest version:

Enjoy!

Dear Codehaus Cargo enthusiasts

We are happy to announce Codehaus Cargo 1.9.4, which includes two minor improvements:

You might wonder, why to have a new release for such small fixes. The answer lies in the way we build Codehaus Cargo: we worked on enabling Dependabot, which ensures dependencies, be it for Codehaus Cargo itself as well as the Maven plugins used in the build process, are updated automatically. And, as you can imagine, just enabling this updated certain core portions of the build process to bump up to major upgrades! These should, nevertheless, be a non-impact for you as a user.

To upgrade to this latest version:

Enjoy!

Dear Codehaus Cargo enthusiasts

We are happy to announce Codehaus Cargo 1.9.3, which includes the below improvements:

  • Core API

    • [CARGO-1556] - Allow setting the JVM classpath using a -classpath or -cp argument set as GeneralPropertySet.JVMARGS or GeneralPropertySet.START_JVMARGS
      This comes on top of the existing methods for setting an extra classpath or an application classpath, and can be useful if you want to, for example, change the container’s Java loggers and these require specific libraries in the JVM classpath

  • Containers - Jetty

    • [CARGO-1554] - Have a user-friendly way of (de)activating Jetty modules
      Please note that this is only for Jetty 10.x and onwards - As even Jetty 9.x has different ways of (de)activating its modules between minor versions…

  • Containers - WildFly

To upgrade to this latest version:

Enjoy!

Copyright 2004-2021. All rights reserved unless otherwise noted.
Click here to read our privacy and cookie policy