Regression!!!! Cargo 1.0-beta-5 does not find deployment dependency in clover forked lifecycle

Description

I recently attempted to upgrade from 0.3.1 to 1.0-alpha-5. Using 0.3.1 Cargo used to successfully deploy my app just fine both when doing a regular build and when doing a clover build "clover:instrument". However, after upgrading to 1.0-alpha-5 my application still deploys correctly when doing a normal build but fails during the clover forced lifecycle with the error below.

Everything works fine if I am using cargo in the same module as the .war. It only fails when cargo is attempting to deploy another module's dependency.

I've attached a test case. To duplicate simply:

run mvn clover:instrument. The build will fail.
run mvn install. The build will succeed.

Change the cargo version to 0.3.1 and everything works fine.

Assignee

Unassigned

Reporter

Mike Youngstrom

Components

Fix versions

Affects versions

Priority

Critical
Configure