RSS
An RSS feed is available.
News
Dear Codehaus Cargo enthusiasts
As announced on our mailing list a couple days back, Apache Ant versions Codehaus Cargo heavily relies on have some security issues, potentially leaking sensitive information or even allow an attacker to inject modified source files into the Codehaus Cargo container configuration generation process.
To ease the upgrade of the Apache Any version used, we are happy to announce Codehaus Cargo 1.8.1, which has one improvement: [CARGO-1528] - Upgrade to Apache Ant 1.9.15.
To switch to this latest version:
Users of the Maven 2 / Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.8.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.8.1/cargo-core-uberjar-1.8.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.8.1/cargo-ant-1.8.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.8.1/cargo-daemon-webapp-1.8.1.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container
Please also do pass this message to any projects you know of, and ensure they upgrade their Codehaus Cargo, and if require Apache Ant, dependencies.
Enjoy!
Dear Codehaus Cargo enthusiasts
We are happy to announce another jump in Codehaus Cargo’s history, version 1.8.0.
As with other such jumps, this comes with the change in the minimum Java version for Codehaus Cargo: our minimum requirement is now Java 8 (of course, you can still set the JAVA_HOME
of the container executions to “any” Java version). Differently from other times, though, the motivations for this change are different:
Contrarily to previous times, Java 7 itself is not “fully EOL” yet: Java 7’s extended support will actually last until July 2022, on the other hand the last public release of Java 7 lacks the support for the TLS 1.2 protocol - which is used by most HTTPS-based Web servers (and hence many Maven2/Maven3 repositories) today - while the “only” way to have such “modern” versions of Java 7 is to have an Oracle Extended Support subscription. That hence made Java 7 very difficult to justify for a free of charge, open source project.
In addition, some parts of Codehaus Cargo which have been backwards compatible to the level where it would be considered “ancient” finally ended up failing us: yes, I’m talking about our various WARs, used for testing and for the Cargo Ping Component, which so far had been using the DTD-based servlet 2.3 definitions. TomEE 9.x has been the first container to drop the support for such ancient servlet versions, we hence have “upgraded” these to servlet 2.4 (which dates back to 2003!), which in turn implies Codehaus Cargo’s support for the “antique” Jetty 4.x and Resin 2.x containers is now gone.
As you know, though, there are many other “old” Java containers that do not work with Java 8. For all these, our Continous Integration system takes advantage of Codehaus Cargo’s flexible JAVA_HOME
definition abilities, and hence runs these containers with Java 7 even though the core build itself (including the tests we execute) are on Java 8. For more details, have a look at how we run our Java samples and the non JDK 8 containers section of our CI configuration.
Here come the full details of what’s new with Codehaus Cargo 1.8.0:
Core
[CARGO-1520] - Upgrade various dependencies to the latest versions compatible with Java 8
[CARGO-1526] - Change the minimum servlet requirement to version 2.4
Containers - Jetty
[CARGO-1527] - Remove Jetty 4.x (as it doesn't support servlet 2.4)
Containers - Resin
[CARGO-1527] - Remove Resin 2.x (as it doesn't support servlet 2.4)
Containers - TomEE
[CARGO-1525] - Add support for TomEE 9.x
To try it out:
Users of the Maven 2 / Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.8.0
Users of the Java API can download the new Uberjar from https://repo.maven.apache.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.8.0/cargo-core-uberjar-1.8.0.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.8.0/cargo-ant-1.8.0.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.8.0/cargo-daemon-webapp-1.8.0.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
The ones who follow our Web site closely most likely noticed two “silent” releases, I decided perhaps it is worthwhile to do a quick blog post and news on our mailing list so we do keep a level of transparency.
Improvement with Codehaus Cargo 1.7.15 in the Tomcat containers:
[CARGO-1522] - Support customizing the tomcat connector protocol with more classes
Improvement with Codehaus Cargo 1.7.16 in the Glassfish and Payara containers:
[CARGO-1524] - Add support for EAR name to Glassfish 3.x onwards and Payara
To try out this latest version:
Users of the Maven 2 / Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.7.16
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.16/cargo-core-uberjar-1.7.16.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.16/cargo-ant-1.7.16.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.16/cargo-daemon-webapp-1.7.16.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.7.14, a version packed with extended support for new versions of containers, and some bug fixes:
Core
[CARGO-1521] - The
ZipUrlInstaller
sends incorrectAccept
headers, which some Web servers reject with an HTTP 406 error
Containers - Jetty
[CARGO-1511] - Document the
JettyPropertySet.DEPLOYER_URL
property
Containers - Tomcat
[CARGO-1519] - Unable to perform a remote redeployment of non-ROOT app with version suffix to Tomcat containers with versioning support when an old version exists
Containers - WildFly
[CARGO-1518] - Add support for WildFly 20.x
This version also includes the below fix, which was fixed as part of Codehaus Cargo 1.7.13 (a version that we chose not to announce):
[CARGO-1517] - The WebLogic 12.2.x container doesn't work with WebLogic 12.2.1.4.0
To try it out:
Users of the Maven 2 / Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.7.14
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.14/cargo-core-uberjar-1.7.14.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.14/cargo-ant-1.7.14.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.14/cargo-daemon-webapp-1.7.14.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.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!