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:
ContainerStopMojonow can resolve dependencies with scope
<test>, the same way
ContainerStartMojocan (CARGO-1069 and CARGO-527).
functional-testsartifact of the Separate Functional Test Module Archetype now uses
packaging=jarand is compatible with m2e (CARGO-1065).
undeploymethod ignored the EAR's name ( CARGO-1076).
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):
ResourceUtils: it now loads resources using a class loader (as opposed to a class, which was the case in the past), hence
AbstractLocalConfiguration.RESOURCE_PATHhas been changed from
"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.
AbstractCopyingInstalledLocalDeployer.setShouldDeployExpanded*smethods have been removed (CARGO-905 and CARGO-940). As a replacement:
Deployabletype has a generic
AbstractCopyingInstalledLocalDeployerhas a generic method
setShouldDeployExpandedwith two arguments.
<artifactInstaller>don't have the
<installDir>attribute anymore, replaced by
cargo.tomcat.manager.url) has been removed (CARGO-965), please use the generic
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:
<version>to 1.2.0, and Maven2/Maven3 will download the new version automatically.
Please share your good (and bad) findings on the firstname.lastname@example.org mailing list.