Codehaus Cargo 1.7.12 is here!
Dear Codehaus Cargo enthusiasts
We are happy to announce Codehaus Cargo 1.7.12, a version packed with extended support for new versions of containers, and some bug fixes:
Containers - Payara
[CARGO-1516] - Codehaus Cargo doesn't work with Payara 5.201
While working on this bugfix, we actually also improved the way thegetVersion
methods are implemented for various containers (such as Jetty, JRun, JBoss / WildFly and Tomcat) by upgrading them with thetry-with-resources
constructs introduced in Java 7.
Containers - Tomcat
[CARGO-1513] - Add support for Tomcat 10.x
Please be aware that Tomcat 10 (at least, the early milestone versions) has been built to be Jakarta EE only, which means thejavax.*
packages are not available. A migration tool is being built to allow applications (even compiled ones) to move, so far it is in early development stages only.
Containers - WebLogic
[CARGO-1515] - Add support for WebLogic 14c
While implementing this, we fixed a very old bug wherenull
values in ANT token replacements would not work, which as a side effects enables us to run the XA datasource tests for supported WebLogic containers. It is interesting that this went unnoticed for so many years!
In addition to these, we have various code cleanups to remove old repositories, also to upgrade the Maven Invoker plugin so our build actually works on Windows with recent Maven 3 versions.
To try it out:
Users of the Maven 2 / Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.7.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.7.12/cargo-core-uberjar-1.7.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.7.12/cargo-ant-1.7.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.7.12/cargo-daemon-webapp-1.7.12.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container
Enjoy!