Codehaus Cargo - Codehaus Cargo 1.9.12 is here

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!

Click here to read our privacy and cookie policy

Quick Links

Containers

Independent extensions

Development