Dear Codehaus Cargo enthusiasts

Again a bit more than a month after our last release, we are happy to announce Codehaus Cargo 1.10.4, which features the below improvement and bug fixes, all around GlassFish and Payara containers

• Bug fix:

  • [CARGO-1599] - Deployment of a default datasource fails in GlassFish 7.x

• Improvements:

  • [CARGO-1597] - Add the ability to set connection pool attributes in GlassFish and Payara

  • [CARGO-1598] - Add the ability to create managed executor service in GlassFish

  • [CARGO-1600] - Add support for Payara 6.x

To upgrade to this latest version:

• Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.10.4

• Users of the Java API can download the new Uberjar from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.10.4/cargo-core-uberjar-1.10.4.jar

• Similarly, users of the Ant tasks can download the new Ant tasks from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-ant/1.10.4/cargo-ant-1.10.4.jar

• Finally, the ones who want to see the Cargo Daemon can get it from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.10.4/cargo-daemon-webapp-1.10.4.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container

Enjoy!

Dear Codehaus Cargo enthusiasts

A bit more than a month after our last release, we are happy to announce Codehaus Cargo 1.10.3, which features one, and probably quite an important, bug fix:

• Core, yet with effects quite visible in the Ant tasks and Maven 3 plugin:

  • [CARGO-1596] Cargo Ant tasks and Maven plugin do not log to console anymore

The ones who read the JIRA release notes will also notice, that we also fixed the issue where deploying application to remote Payara on another host doesn't work because the "upload" step is somehow skipped (referenced CARGO-1588), which has been mostly a documentation update.

To upgrade to this latest version:

• Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.10.3

• Users of the Java API can download the new Uberjar from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.10.3/cargo-core-uberjar-1.10.3.jar

• Similarly, users of the Ant tasks can download the new Ant tasks from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-ant/1.10.3/cargo-ant-1.10.3.jar

• Finally, the ones who want to see the Cargo Daemon can get it from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.10.3/cargo-daemon-webapp-1.10.3.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container

Enjoy!

Dear Codehaus Cargo enthusiasts

Exactly one month after switching to a 1.10.x branch, we are happy to announce the immediate availability of Codehaus Cargo 1.10.2, which mainly features bug fixes:

• Core:

  • [CARGO-1595] Race condition in the Codehaus Cargo JVM launcher

  • [CARGO-1593] Codehaus Cargo can't merge filter-mapping (nor servlet-mapping) completely

• Extensions - Maven 3 plugin:

  • [CARGO-968] Remove redundant <default> tag from uberwar merge descriptor

In particular, the fix for the race condition gets rid of awkward, difficult to replicate behaviour where Codehaus Cargo cannot detect the JVM version, and throws “random”, hard to understand exceptions.

To upgrade to this latest version:

• Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.10.2

• Users of the Java API can download the new Uberjar from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.10.2/cargo-core-uberjar-1.10.2.jar

• Similarly, users of the Ant tasks can download the new Ant tasks from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-ant/1.10.2/cargo-ant-1.10.2.jar

• Finally, the ones who want to see the Cargo Daemon can get it from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.10.2/cargo-daemon-webapp-1.10.2.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container

Enjoy!

Dear Codehaus Cargo enthusiasts

We are glad to announce the immediate availability of Codehaus Cargo 1.10.1!

The change to a 1.10.x branch indeed comes with some updates, namely the removal of Apache Ant as a core dependency, and upgrade to JDOM 2.x (as JDOM 1.x is now 10 years old!). This has multiple implications:

• Our Installers now support newer formats, such as 7Z, while the JVM controller gets new features under the hood (such as forcibly killing stalled JVMs).

• The feature allowing SSH-based remote Java container executions is now gone, any users would need to switch to Cargo Daemon instead.

• For the ones using Codehaus Cargo’s containers and other capabilities via its Maven 3 plugin, there are no changes - All changes under the hood, as well as the dependency updates, are handled by Maven itself.

• For the ones using Codehaus Cargo’s containers and other capabilities, in particular for the ones either making use of the Java APIs directly or the Ant tasks: the Apache Ant libraries are not a dependency anymore, and Codehaus Cargo 1.10.x onwards will rely on commons compress 1.21 or greater as well as JDOM 2.0.6.1 or greater.

• For the ones who developers containers on top of Codehaus Cargo, there are API changes as the Ant file filters are not used anymore, and we instead have replacement maps. You hence will have to perform small adaptations to your own code.

We also gave some new features, namely support for new containers (though both are in milestone and alpha stages, respectively):

• Added support for GlassFish 7.x.

• Added support for WildFly 27.x.

To upgrade to this latest version:

• Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.10.1

• Users of the Java API can download the new Uberjar from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.10.1/cargo-core-uberjar-1.10.1.jar

• Similarly, users of the Ant tasks can download the new Ant tasks from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-ant/1.10.1/cargo-ant-1.10.1.jar

• Finally, the ones who want to see the Cargo Daemon can get it from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.10.1/cargo-daemon-webapp-1.10.1.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container

Enjoy!

Dear Codehaus Cargo enthusiasts

We are glad to announce that Codehaus Cargo 1.9.12 is now available! This version includes two bug fixes:

• Core:

  • [CARGO-1583] - Codehaus Cargo doesn't properly check that the provided JVM executable is valid

• Containers - JBoss / Jetty:

  • [CARGO-1584] - The Jetty standalone / embedded standalone container as well as some JBoss standalone containers don't work with Java 17.0.3 as well as Java 11.0.15 due to an XPath issue

That last item is actually caused by an XPath bug in the JRE that got recently introduced in Java 11.0.15, Java 17.0.3 and potentially other versions. As a result, if you “all of a sudden” (or, more precisely, after upgrading your Java version) start getting messages such as org.codehaus.cargo.util.CargoException: Node [...] not found in file [...].xml, then you should upgrade to this latest version of Codehaus Cargo. To date, no Java release has a fix for that recently introduced XPath bug.

To upgrade to this latest version:

• Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.9.12

• Users of the Java API can download the new Uberjar from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.9.12/cargo-core-uberjar-1.9.12.jar

• Similarly, users of the Ant tasks can download the new Ant tasks from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-ant/1.9.12/cargo-ant-1.9.12.jar

• Finally, the ones who want to see the Cargo Daemon can get it from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.9.12/cargo-daemon-webapp-1.9.12.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container

Enjoy!