RSS
An RSS feed is available.
News
Dear CARGO enthusiasts
CARGO's first version in 2013, version 1.3.2, is now ready! This new version fixes the below issues:
- Containers - JBoss:
- JBoss 7.x and JBoss 7.1.x containers now support
ServletPropertySet.USERS
(CARGO-1163) - The JBoss 7.x and 7.1.x Remote Deployer now handles disconnections properly, avoiding
JBREM000200 ERROR
logs on the JBoss console (CARGO-1164)
- JBoss 7.x and JBoss 7.1.x containers now support
- Containers - Tomcat:
AbstractTomcatManagerDeployer
now throws an exception if theundeploy
operation is called for a deployable which is not deployed (CARGO-1167)- Default user role now work with management application in Tomcat 7.x (CARGO-1165)
TomcatManagerInstalledLocalDeployer
now has an implementation for Tomcat 7.x (CARGO-1166)
- CARGO Daemon:
- The Daemon WAR now works properly with various servers, Jetty, Glassfish and Tomcat have been tested (CARGO-1161)
- Maven2/Maven3 plugin:
- The deployer
pingTimeout
logs are now displayed properly (CARGO-1168) - The behaviour when a non-absolute path is specified in plugin / task configuration has been improved (CARGO-1162)
- The deployer
To upgrade to this new version:
- Users of the Maven2/Maven3 plugin simply need to use the CARGO plugin version 1.3.2.
- Users of the Java API can download the new Uberjar from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.3.2/cargo-core-uberjar-1.3.2.jar
- Similarly, users of the ANT tasks can download the new ANT tasks from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-ant/1.3.2/cargo-ant-1.3.2.jar
- Finally, the ones who want to use the Cargo Daemon can download the webapp from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.3.2/cargo-daemon-webapp-1.3.2.war
Enjoy!
Dear CARGO enthusiasts
A few weeks after version 1.3.0, CARGO 1.3.1 is now ready -with the fixes for the below issues:
- JBoss
- JBoss 7.x and 7.1.x local deployer does not take into account WAR context if a shared or extra classpath needs to be set [CARGO-1156]
- JBoss 7.x or 7.1.x datasource classes cannot come from shared classpath [CARGO-1157]
- Jetty:
- Upgrade the Jetty 9.x container to support Jetty 9.0.0.M1 and 9.0.0.M2 [CARGO-1152]
- WebSphere
- WebSphere deployment fails for WARs with
<display-name>
set [CARGO-1153] - Daemon
- CARGO daemon does not work with Jetty [CARGO-1155]
- Daemon Java client cannot start container when
ZipUrlInstaller
is set [CARGO-1158] - Daemon Java client throws NullPointerException if no deployables have been set [CARGO-1159]
- NullPointerException on daemon webapp in some situation [CARGO-1154]
It also comes with one small improvement: the directory where to deploy web archives for Tomcat installed containers is now taken from server.xml file [CARGO-455]. Moreover, we have added some automated tests for the Cargo Daemon [CARGO-1150].
To upgrade to this new version:
- Users of the Maven2/Maven3 plugin simply need to use the CARGO plugin version 1.3.1.
- Users of the Java API can download the new Uberjar from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.3.1/cargo-core-uberjar-1.3.1.jar
- Similarly, users of the ANT tasks can download the new ANT tasks from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-ant/1.3.1/cargo-ant-1.3.1.jar
- Finally, the ones who want to use the Cargo Daemon can download the webapp from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.3.1/cargo-daemon-webapp-1.3.1.war
Enjoy!
Dear CARGO enthusiasts
Our next big release of CARGO, version 1.3.0, is now available! It comes with a lot of very attractive new features:
- The newest and latest Jetty 9.x is supported [CARGO-1147]
- IBM WebSphere 8.5.x container has been added -making another very old CARGO ticket get solved! [CARGO-147]
- We have introduced a new feature, the Cargo Daemon: this is a Web-based application that uses the Cargo API to configure, start and stop containers on a remote machine. The daemon is meant to be listening 24/7, to allow users to deploy new containers and web applications at their command. It can be accessed using a browser-based UI, via Java API or Maven2 plugin. [CARGO-1148]
- Local and embedded deployer support has been added to the ANT plugin [CARGO-1144]
The Apache Geronimo container has been improved a lot as well:
- Bundle support has been added to Geronimo 3.x [CARGO-1143]
- Extra classpath can now be set on Geronimo 2.x and 3.x [CARGO-1145]
- It is now possible to define datasources on Geronimo 2.x and 3.x [CARGO-1146]
We have also fixed some JBoss issues (all of them on JBoss 7.x and 7.1.x):
- Non-default deployment directory is now supported [CARGO-1141]
GeneralPropertySet.RUNTIME_ARGS
is now set at the correct place [CARGO-1139]- Extra and shared classpath is now fully supported [CARGO-1149]
As for the other fixes and improvements:
- Direct configuration of SSL/TLS connector options for Tomcat 5.x, 6.x, and 7.x stand alone local configurations is allowed [CARGO-1135]
- OC4J's MIME types now has text/css [CARGO-281]
- Property injection from Maven
settings.xml
has been fixed [CARGO-1136] - Non 200 HTTP status codes are accepted by the deployment's ping component [CARGO-1118]
- Shared classpath for WARs are now supported on Jetty [CARGO-948]
To try this new version:
- Users of the Maven2/Maven3 plugin simply need to use the CARGO plugin version 1.3.0.
- Users of the Java API can download the new Uberjar from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.3.0/cargo-core-uberjar-1.3.0.jar
- Similarly, users of the ANT tasks can download the new ANT tasks from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-ant/1.3.0/cargo-ant-1.3.0.jar
- Finally, the ones who want to use the Cargo Daemon can download the webapp from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-daemon-webapp/1.3.0/cargo-daemon-webapp-1.3.0.war
Enjoy!
Dear CARGO users
After about one month from the last release, CARGO 1.2.4 is now here! It comes with three important new features:
- WebLogic 12.x support has been added (CARGO-1132)
- Geronimo 3.x is now supported (CARGO-1126)
- Geronimo 2.x and 3.x containers are able of working with existing standalone configurations (CARGO-1127)
- Jetty 8.x now supports ServletContainerInitializers (CARGO-1133)
Apart form that, this versions also comes with some bug fixes:
- Exception messages when the user defines no ContainerId but uses a ZipUrlInstaller or ArtifactInstaller have been improved (CARGO-1128)
- Exception messages when one attempts to use a local deployer for a non-existing directory have been improved (CARGO-1131)
- Cargo plugin does not expect to be executed from inside .jar anymore (CARGO-1129)
Full release notes are accessible on https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18669&styleName=Html&projectId=10730
To try this new version:
- Users of the Maven2/Maven3 plugin simply need to use the CARGO plugin version 1.2.4.
- Users of the Java API can download the new Uberjar from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.2.4/cargo-core-uberjar-1.2.4.jar
- Similarly, users of the ANT tasks can download the new ANT tasks from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-ant/1.2.4/cargo-ant-1.2.4.jar
Enjoy!
Dear CARGO enthousists.
After about two months from the last release, CARGO 1.2.3 is now ready.
This new version comes with only one new feature, support for setting JBoss AJP ports (CARGO-1112).
Apart from that, this version fixes the below bugs:
- ANT tasks and Maven2/Maven3 plugin:
- The
cargo:run
MOJO and run ANT task now try to stop the container (via shutdown hook) whenCTRL + C
is pressed (CARGO-1124) - Maven2/Maven3 plugin fixes:
cargo:run
now deploys all WARs; as the <deployables> element has been centralized (CARGO-1114)- The intreaction between the CARGO Maven2/Maven3 plugin and Maven proxy settings have been reviewed to function in an homogeneous manner (CARGO-1119 and CARGO-1121)
- General fixes:
- The configuration of
<cargo.servlet.users>
does not require a role anymore (CARGO-526) - Container-specific fixes:
- Jetty 7.x and 8.x Remote Deployment now works properly if Jetty-JNDI is active (CARGO-1122 and CARGO-1123)
- Jetty installed local deployer has been fixed to be able of deploying sub-contexts (CARGO-1125)
jboss.server.lib.url
is now correctly handled (CARGO-1110)- WARs can now be deployed on JBoss 7.x and 7.1.x containers' root context (CARGO-1090)
- JBoss 7.x and 7.1.x contains' bind address can now be set to
0.0.0.0
(CARGO-1111) - Tomcat NIO connectors now work properly with CARGO (CARGO-1115)
The full release notes are accessible on https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18524&styleName=Html&projectId=10730
To try this new version:
- Users of the Maven2/Maven3 plugin simply need to use the CARGO plugin version 1.2.3.
- Users of the Java API can download the new Uberjar from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-core-uberjar/1.2.3/cargo-core-uberjar-1.2.3.jar
- Similarly, users of the ANT tasks can download the new ANT tasks from http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-ant/1.2.3/cargo-ant-1.2.3.jar
We have another amazing news to share: over the last 12 months, overall download count of the CARGO components have gone up 60%. See below, for example, for the Maven2/Maven3 plıugin:
We thank you again for your continuing interest.
Enjoy!