RSS
An RSS feed is available.
News
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:
- 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
Enjoy!
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:
- [CARGO-1089] - pingUrl and pingTimeout doesn't work with cargo:start
- 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!
Dear CARGO enthusiasts
First of all, happy New Year!
Since the last release of CARGO a bit more than one month and a half ago, we have had the opportunity of fixing some bugs and adding the functionalities:
- CARGO Maven2/Maven3 plugin fixes and improvements:
ContainerStopMojo
now can resolve dependencies with scope<test>
, the same wayContainerRunMojo
andContainerStartMojo
can (CARGO-1069 and CARGO-527).- The
functional-tests
artifact of the Separate Functional Test Module Archetype now usespackaging=jar
and is compatible with m2e (CARGO-1065). - The CARGO plugin now resolves the required container JARs automatically (CARGO-975), meaning that if you're for example only using CARGO with the Jetty container than the other containers' JARs will not be downloaded.
- Fixed a bug where the JSR-88 deployers' (used by the GlassFish remote deployer)
undeploy
method ignored the EAR's name ( CARGO-1076). - All CARGO JBoss containers, from the 10-year-old JBoss 3.x to the brand-new JBoss 7.1.x, now support datasources (CARGO-426). You can therefore now use CARGO to deploy datasources to any JBoss container; the bigger advantage being that the datasource definitions don't need to change between JBoss versions nor between all containers that CARGO can deploy datasources to.
- The JOnAS remote deployer now works with Windows for XML deployment plans (CARGO-1067).
- The Resin container has been improved:
- The Resin management port can be configured (CARGO-318)
- Resin 3.1.x support has been added (CARGO-759 and CARGO-494)
- Last but not least, the new XML replacement API introduced in CARGO 1.1.4, which avoids having CARGO-specific container configuration files in the distribution, is now used more extensively; as the Jetty (CARGO-1060), Resin (CARGO-1075) and Tomcat (CARGO-1061) container also make use of it.
- This way, not only we won't have to maintain these CARGO-specific files manually anymore, but also new versions will be supported "out of the box" and CARGO will also work with different flavours of containers.
CARGO 1.2.0 is therefore now ready. Please note that on the API side, this new minor version comes with some behavioural changes and the removal of some elements (which have been deprecated for over 6 months now):
- To achieve automatic resolution of container JARs in the Maven2/Maven3 container, a small change has been done in the
ResourceUtils
: it now loads resources using a class loader (as opposed to a class, which was the case in the past), henceAbstractLocalConfiguration.RESOURCE_PATH
has been changed from"/org/codehaus/cargo/container/internal/resources/"
to"org/codehaus/cargo/container/internal/resources/"
(without the slash at the beginning). If your code uses the same constant, make sure you update it properly. - The
Deployable.isExpanded*
andAbstractCopyingInstalledLocalDeployer.setShouldDeployExpanded*s
methods have been removed (CARGO-905 and CARGO-940). As a replacement: - The
Deployable
type has a genericisExpanded
method. AbstractCopyingInstalledLocalDeployer
has a generic methodsetShouldDeployExpanded
with two arguments.- File handling methods that manipulate texts now need to specify the encoding (CARGO-909).
- In the Maven2/Maven3 plugin, the
<zipUrlInstaller>
and<artifactInstaller>
don't have the<installDir>
attribute anymore, replaced by<downloadDir>
and<extractDir>
attributes (CARGO-916). TomcatPropertySet.MANAGER_URL
(i.e.cargo.tomcat.manager.url
) has been removed (CARGO-965), please use the genericRemotePropertySet.URI
(i.e.cargo.remote.uri
) instead.
You can access the full release notes by visiting https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17088&styleName=Html&projectId=10730
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.0, and Maven2/Maven3 will download the new version automatically.
Please share your good (and bad) findings on the user@cargo.codehaus.org mailing list.
Enjoy!
Dear CARGO enthusiasts
About 8 weeks have passed since the last CARGO release. During these weeks, some fixes and improvements have been implemented in CARGO and the new version 1.1.4 is now ready. These changes include:
- General:
- Harmonized the behaviour when copying configuration files, now both
<file>
and<configfiles>
can copy directories [CARGO-1045] - Improved the module hierarchy and dependencies [CARGO-1011]
- This way, the CARGO Maven2 plugin doesn't use the uberjar anymore but rather the individual artifacts
- Cleaned notes about old CARGO versions from documentation [CARGO-997]
- Corrected Javadoc for
MergeStrategy.inRight()
[CARGO-1046]
- Harmonized the behaviour when copying configuration files, now both
- JBoss:
- JBoss 7.1.0 beta 1 is now supported [CARGO-1063]
- The JBoss 5.x and 6.x remote deployers now take into account username and password [CARGO-1058]
- JBoss 5.x, 5.1.x, 6.x, 6.1.x and 7.x local containers don't have cargo-specific XML files anymore [CARGO-839]
- Jetty:
- Fixed compatibility issues between the remote Jetty deployer and jetty-hightide (Jetty@Codehaus) [CARGO-983]
- Remote Jetty deployer now works with Jetty 8.x with the default OPTIONS [CARGO-1049]
- Fixed the default CARGO OPTIONS for the Jetty 8.x container [CARGO-1050]
- JOnAS:
- Remote deployer can now undeploy deployment plans on JOnAS 5.x [CARGO-1047]
- The standalone JOnAS container can now set any JOnAS configurator property [CARGO-1054]
- The modular ANT tasks are used when configuring the latest JOnAS 5.3 milestones [CARGO-1057]
- The JOnAS remote deployer has a new "ignore version" option [CARGO-1048]
- GlassFish:
GlassFish2xAsAdmin
now takes into account the timeout set in the container [CARGO-1055]
- Maven2/Maven3 plugin:
- Different executions can now have different configuration options [CARGO-1053]
You can access the full release notes by visiting https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17845&styleName=Html&projectId=10730
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.1.4, and Maven2/Maven3 will download the new version automatically.
Please share your good (and bad) findings on the user@cargo.codehaus.org mailing list.
Enjoy!