RSS
An RSS feed is available.
News
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 asGeneralPropertySet.JVMARGS
orGeneralPropertySet.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 withcontainerId
andcontainerUrl
[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-pluginChange 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!
Dear Codehaus Cargo enthusiasts
A couple weeks after our last release, please give a warm welcome to Codehaus Cargo 1.8.5! This new version has many “under the hood” changes (in particular, around the dependency versions we use) and features the below improvements:
Extensions - Maven 2 / Maven 3 plugin
[CARGO-1543] - Added
tomcat-dbcp
to the embedded Tomcat container classpath[CARGO-1501] - Mojos that are thread safe should be marked with the appropriate annotation so that maven can run parallel builds
Note: Though Codehaus Cargo itself is thread safe, we would recommend to use this feature with great care: you are most likely using Codehaus Cargo to perform integration tests on containers, you might run into port number clashes when executing the containers in parallel if you’re not careful.
This will also be our last 1.8.x
version, the reason being that the current Maven 2 / Maven 3 plugin (which behind the scenes is a Maven 2 plugin which Maven 3 can also use) will be removed and become a Maven 3 only plugin. This is quite nicely in line with the Maven 2.x end of life from November 2009.
To try out this latest version:
Users of the Maven 2 / Maven 3 plugin simply need to use the Codehaus Cargo plugin version 1.8.5
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.5/cargo-core-uberjar-1.8.5.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.5/cargo-ant-1.8.5.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.5/cargo-daemon-webapp-1.8.5.war and either use the WAR directly as an executable JAR or as a WAR file deployed on another Web container
Enjoy!