Hi CARGO enthusiasts;
It has been more than usual since we did not come up with any new versions, and it is for a good reason: we have been working on CARGO's version 1.1.0. As usual, we have many bug fixes; but most notably we have very interesting new features.
Some of the interesting new features would perhaps be the following:
ZipUrlInstallernow reuses the proxy settings from Maven (CARGO-517)
ZipUrlInstallernow has different download and extraction directories (CARGO-907), and the default extraction directory for the Maven2/Maven3 plugin is the project's build directory (CARGO-908).
Deployable.pingUrlnow supports authentication (CARGO-813)
As for some of the improvements:
Container.stopmethod now waits for the whole server to stop (CARGO-918), which results in more stable tests if containers are started and stopped one after the other.
reloadableparameter can now be configured (CARGO-461)
TomcatLocalInstalledLocalDeployer.shouldCopyWars()has been made configurable (CARGO-963)
And some fixes:
asadminwrapper now correctly reports back errors (CARGO-914)
cargo:startdoes not fail with some versions of JBoss deployables when there's no internet connection (CARGO-956)
And, finally, some major changes that you probably won't notice (but which are one of the reasons why we changed the version number to 1.1.0):
... as well as some major changes you should take a note of:
waitparameter on the ANT and Maven2/Maven3 plugins is now
mvn cargo:start -Dwait=truewhen you want to run manual tests.
ZipUrlInstallernow has different download and extraction directories (CARGO-907), which makes the
installDirproperty obsolete: it is replaced by
extractDir, the old property set them both but will probably removed in CARGO 1.2.0.
TomcatPropertySet.MANAGER_URLhas been deprecated in favor of
TomcatLocalInstalledLocalDeployer.shouldCopyWars()is set to
trueby default (used to be
Deployable.isExpanded*()have been consolidated, obsoleting the
AbstractCopyingInstalledLocalDeployer.setShouldDeployExpanded()have been consolidated, obsoleting the
For a full list, you can always check the release notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10730&version=16436 -we have more than 80 changes!
To use this new version:
<version>to 1.1.0, and Maven2/Maven3 will download the new version automatically.
Please share your good (and bad) findings on the email@example.com mailing list.