Cargo 1.0.2 had the url for the old Codehaus release repo defined in some poms. In the migration to the new Cargo (Nexus hosted) release repo, all Cargo artifacts were moved.
For some reason, when executing Cargo 1.0.2 via the Maven 2 plugin, Maven tries to retrieve artifacts from the old Codehaus repo before trying central. Although we've put redirects in place for the old repo, Maven treats the http redirect response as the actual artifact. Thus, we get incorrect artifacts downloaded and Maven fails. See the attached example.