RSS
An RSS feed is available.
News
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!
Dear Codehaus Cargo enthusiasts
We are happy to announce Codehaus Cargo 1.9.11, which includes the below bug fix and improvement:
Containers - WebLogic and WebSphere
[CARGO-1582] - Allow external scripts executed using WLST to use the property placeholder feature Codehaus Cargo provides
Extensions - Maven 3 plugin, more precisely with the Tomcat container
[CARGO-1580] - Issue with the Tomcat 8.x and 9.x embedded containers in the Maven 3 plugin:
SEVERE: Cannot instantiate an authenticator of class [org.apache.catalina.authenticator.FormAuthenticator]
To upgrade to this latest version:
Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.9.11
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.11/cargo-core-uberjar-1.9.11.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.11/cargo-ant-1.9.11.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.11/cargo-daemon-webapp-1.9.11.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.10 is now available! This version includes some new features:
Containers - JBoss / WildFly:
[CARGO-1577] - Provide an option to keep the original WAR file name when the JBoss or WildFly WAR file has the context root set in the
jboss-web.xml
file
Extensions - Ant:
[CARGO-1578] - Allow container configuration properties to be set using Ant build properties
Extensions - Maven 3 plugin:
[CARGO-1579] - Allow container configuration properties to be set using Maven build properties
To upgrade to this latest version:
Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.9.10
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.10/cargo-core-uberjar-1.9.10.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.10/cargo-ant-1.9.10.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.10/cargo-daemon-webapp-1.9.10.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
It is almost Christmas - As all of you have been very good for Santa, we have received Codehaus Cargo 1.9.9! This version includes some new features and bug fixes:
Containers - Payara
We did some changes, discovered when analyzing CARGO-1575, so that the
payara-p1
versions would not be needed anymore
Containers - WildFly
[CARGO-1571] - Add support for WildFly 25.x
This was actually added with our version 1.9.8, yet we didn’t announce that version so we share it here[CARGO-1576] - Add support for WildFly 26.x
We have also done some changes under the hood, with the way some items are logged and/or shown in stack traces, to help with diagnosing issues similar to CARGO-1574 where the HTTP(S)-based deployer actions would have issues.
To upgrade to this latest version:
Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.9.9
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.9/cargo-core-uberjar-1.9.9.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.9/cargo-ant-1.9.9.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.9/cargo-daemon-webapp-1.9.9.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 happy to announce Codehaus Cargo 1.9.7, which includes the below two bug fixes and one improvement:
Containers - Tomcat
[CARGO-1567] - Cannot configure HTTPS / TLS on Tomcat 10.x / TomEE 9.x
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
andHttpFormRequest
instead of individualHttpURLConnection
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:
Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.9.7
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.7/cargo-core-uberjar-1.9.7.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.7/cargo-ant-1.9.7.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.7/cargo-daemon-webapp-1.9.7.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container
Enjoy!