Comment 2 for bug 1031653

I have checked in a change to the build tools that should solve this problem. What was happening was that wget would encounter a download that used HTTPS and the server had a self signed certificate (snapshots and releases are guilty of this) and wget would reject the download. Unfortunately we were using wget -q, so it failed silently which made the bug non-obvious.

I have updated the scripts to use wget -nv --no-check-certificate instead of wget -q. This means that we will always download files from HTTPS servers, even if the certificate is invalid and -nv instructs wget to not be verbose, which seems to be a semi-quiet option. It will tell you about warnings and errors in the log, but not print a progress bar.

Hopefully this will solve our current problems and make future ones more obvious.