Cargo does not fail correctly when the downloaded ZIP file is broken

Description

The download of the Wildfly 8.x server (126MB) failed and the wildfly-8.2.0.Final.zip file was only 11MB in the default folder (${java.io.tempdir}/installs).

The cargo.log has no indication of any kind of failure:

I changed the downloadDir to a local folder to make the file download again:

This time it failed at 120MB and the ZIP file was corrupt again.

The issue is with our corporate proxy, corrupting files when the proxy thinks that it contains some kind of malware.

But still Cargo should have some checks that the downloaded ZIP file is OK and it should not tell the user that everything is fine in such a case.

In both cases the Maven build fails later with the following error:

Assignee

S. Ali Tokmen

Reporter

MichaelR

Components

Fix versions

Affects versions

Priority

Major
Configure