Cargo : News

RSS


An RSS feed is available.

News


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:

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:

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) when CTRL + 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:

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!

CARGO 1.2.2 available!

Dear CARGO enthusiasts

After about 7 weeks after the last release, I decided we have enough changes and fixed bugs in order to go ahead with CARGO 1.2.2. As for what's new, the list is this time small (12 entries):

Improvements and new features (5)

    • Jetty containers now support datasources (CARGO-1107)
    • Jetty 7.x standalone local container is now the default container for the CARGO Maven2/Maven3 plugin (CARGO-1106) and downloads its container via the artifactInstaller
    • The usage of an external jetty-env.xml file has finally been documented (CARGO-861)
    • The XML/properties replacement engine can now WARN when a replacement is not possible (instead of failing) (CARGO-1099)
    • Deployers (and mostly undeployers) can now intelligently ignore failures when deploy/undeploy fails (for example, if the application is not deployed but one attempts to undeploy it) (CARGO-1100)

Bug fixes (7)

    • Proxies that would be previously set by Maven are not used during deployment anymore (CARGO-1042)
    • Module names in JBoss do not contain any periods anymore -allowing the deployment of datasources via Maven2/Maven3 plugin (CARGO-1091)
    • Logging level is now interpreted properly for containers that output their messages on stderr (CARGO-1095)
    • Jetty can deploy to root (/) context (CARGO-1103)
    • cargo.jboss.invoker.pool.port configuration property works properly for JBoss 5+ (CARGO-1104)
    • Merging of XML files doesn't throw a ConcurrentModificationException anymore (CARGO-1105)
    • JVM properties on Glassfish now work (CARGO-1108)

In addition to these, we have done various changes in the documentation as well as the Maven archetypes. For example, a profile for JBoss 7.1.x has been added to all archetypes and is configured with an artifactInstaller.

The full release notes can be found on https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18384&styleName=Html&projectId=10730

To use this new version:

  • Users of the Java API and/or the ANT tasks can download the required components (be it the uberjar, ANT tasks and others) via the CARGO Downloads page.
  • Users of the Maven2/Maven3 plugin simply need to change their plugin version to 1.2.2.

Please provide your feedback to the user@cargo.codehaus.org mailing list.

Enjoy!

Dear CARGO enthusiasts

CARGO 1.2.1 is now available; and no this is definitely not an April fool!

Of course, all of you are wondering what that release brings in... As usual, we have a certain number of fixes and improvements; major highlights are:

  • 12 bug fixes, be it for core components but also for containers.
  • CARGO now supports starting an installed local container independently from the starting instance (Java API, ANT or Maven2/Maven3 plugin); so that the started container can "outlive". This new feature is called spawning.
  • The Jetty container now supports existing local configuration.
  • JBoss 7.1.0 and 7.1.1 (Final versions) are supported.
  • The XML merger (i.e., uberwar) now does a much more careful work when it comes to merging duplicate XML entities.

To use this new version:

  • Users of the Java API and/or ANT tasks can download the CARGO uberjar and ANT tasks from the download page: http://cargo.codehaus.org/Downloads
  • Maven2/Maven3 users simply need to change the plugin's <version> to 1.2.1, and Maven2/Maven3 will download the new version automatically.

Please share your good (and bad) findings on the user@cargo.codehaus.org mailing list.

As usual, for those who are wondering, please find below the full change list:

  • The following issues with the XML merger (i.e., uberwar) have been fixed:
    • [CARGO-1078] - Duplicate entries when merging <filter-mapping>
    • [CARGO-1080] - Duplicate entries when merging servlet mappings
    • [CARGO-1081] - Duplicate entries when merging security constraints
    • [CARGO-1094] - Duplicate init-param element when merging filter
    • [CARGO-1096] - XML merger adds xmlns="" entries
  • JBoss-specific fixes:
    • [CARGO-1086] - CARGO doesn't work with JBoss 7.1.0.Final
    • [CARGO-1087] - remote deployment to JBoss AS 7.1.0.Final in standalone configuration leads to javax.security.sasl.SaslException
    • [CARGO-1088] - Undeploy fails with a non-farm configuration
  • Jetty-specific fixes:
    • [CARGO-1085] - WAR authentication does not work with embedded Jetty 7.6.x and 8.1.x
  • GlassFish-specific fixes:
    • [CARGO-1077] - Standalone GlassFish configuration deletes all existing GlassFish domain when started
  • Tomcat-specific fixes:
    • [CARGO-1082] - CARGO does not create the list of roles in the Tomcat users XML
  • Fixes relating to the Maven2/Maven3 plugin:

 

  • General improvements:
    • [CARGO-364] - Allow spawned execution of an local containers to enable the app server to outlive the calling CARGO application (Java API, ANT or Maven2/Maven3)
  • XML merger (i.e., uberwar) improvements:
    • [CARGO-1079] - Add support for merging <mime-mapping>
  • Jetty-specific improvements:
    • [CARGO-1083] - Add Jetty support to existing local configuration for installed container
    • [CARGO-1093] - Allow jetty existing local container to start using only configuration on the server
  • GlassFish-specific improvements:
    • [CARGO-1071] - Allow to start GlassFish domain in debug mode
    • [CARGO-1072] - Allow to set GlassFish debugger port
  • Improvements on the Maven2/Maven3 plugin
    • [CARGO-1097] - Make use of maven artifact when computing location for deployable and dependency

You can also see the HTML release notes via https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18290&styleName=Html&projectId=10730

Enjoy!