Dear Codehaus Cargo enthusiasts

We are happy to announce Codehaus Cargo 1.9.4, which includes two minor improvements:

• Core API

  • [CARGO-1561] - Ensure WAR contexts are "clean"

• Extensions - Maven 3 plugin

  • [CARGO-1562] - When no containers are specified, use Jetty 9.x (instead of the current Jetty 8.x)

You might wonder, why to have a new release for such small fixes. The answer lies in the way we build Codehaus Cargo: we worked on enabling Dependabot, which ensures dependencies, be it for Codehaus Cargo itself as well as the Maven plugins used in the build process, are updated automatically. And, as you can imagine, just enabling this updated certain core portions of the build process to bump up to major upgrades! These should, nevertheless, be a non-impact for you as a user.

To upgrade to this latest version:

• Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.9.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.9.4/cargo-core-uberjar-1.9.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.9.4/cargo-ant-1.9.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.9.4/cargo-daemon-webapp-1.9.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

We are happy to announce Codehaus Cargo 1.9.3, which includes the below improvements:

• Core API

  • [CARGO-1556] - Allow setting the JVM classpath using a -classpath or -cp argument set as GeneralPropertySet.JVMARGS or GeneralPropertySet.START_JVMARGS
    This comes on top of the existing methods for setting an extra classpath or an application classpath, and can be useful if you want to, for example, change the container’s Java loggers and these require specific libraries in the JVM classpath

• Containers - Jetty

  • [CARGO-1554] - Have a user-friendly way of (de)activating Jetty modules
    Please note that this is only for Jetty 10.x and onwards - As even Jetty 9.x has different ways of (de)activating its modules between minor versions…

• Containers - WildFly

  • [CARGO-1558] - Add support for WildFly 23.x

To upgrade to this latest version:

• Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.9.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.9.3/cargo-core-uberjar-1.9.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.9.3/cargo-ant-1.9.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.9.3/cargo-daemon-webapp-1.9.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

About 4 weeks passed since our last release, and we are happy to announce Codehaus Cargo 1.9.2, which includes some bug fixes and under the hood improvements:

• Build process

  • [CARGO-1529] - Further changes to update code standards to Java 8, by removing the org.codehaus.cargo.util.Base64 class and using the Java 8+ standard classes instead

• Containers - Tomcat

  • [CARGO-1534] - Tomcat embedded local containers show a No global web.xml found error when starting

• Extensions - Daemon

  • [CARGO-1552] - Make the daemon container status refresh and log viewer more stable

• Extensions - Maven 3 plugin

  • [CARGO-1553] - mvn commands not working with containerId and containerUrl

  • [CARGO-1551] - Upgrade the JUnit version used in Maven Archetypes to JUnit 5

To upgrade to this latest version:

• Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.9.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.9.2/cargo-core-uberjar-1.9.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.9.2/cargo-ant-1.9.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.9.2/cargo-daemon-webapp-1.9.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

Only a few days after the release of Codehaus Cargo 1.9.0, we are happy to release its first bug fix version 1.9.1. This version comes with the below bug fixes and improvements:

• Build process

  • [CARGO-1545] - Cannot generate aggregate javadoc

• Containers - JBoss

  • [CARGO-1546] - JBoss 5.x to 7.1.x remote deployers are broken

• Containers - Payara

  • [CARGO-1547] - After upgrade to cargo-maven3-plugin:1.9.0 cannot start Payara

• Containers - WebSphere

  • [CARGO-1548] - Broken WebSphere commands

• Extensions - Maven 3 plugin

  • [CARGO-1549] - Align and centalize dependency and plugin versions used in Maven archetypes and samples

To try out this latest version:

• Users of the Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.9.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.9.1/cargo-core-uberjar-1.9.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.9.1/cargo-ant-1.9.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.9.1/cargo-daemon-webapp-1.9.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

As announced two days ago, Codehaus Cargo 1.9.0 is now ready, and features one and only change:

• Extensions - Maven 3 plugin

  • [CARGO-1544] - Upgrade the Codehaus Cargo Maven plugin to Maven 3
    Note: This implies that we don’t have a Maven 2 plugin anymore, and only a Maven 3 plugin.

Though this change is quite nicely in line with the Maven 2.x end of life from November 2009, it does imply slightly some more work from your side than usual.

To try out this latest version:

• Users of the Maven 3 plugin need to do two things:

  • Switch to the new artifactId for the Codehaus Cargo plugin: cargo-maven3-plugin

  • Change the plugin version 1.9.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.9.0/cargo-core-uberjar-1.9.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.9.0/cargo-ant-1.9.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.9.0/cargo-daemon-webapp-1.9.0.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container

Enjoy!