There is a bit of a problem with people using the wrapper. I am trying to swap our website build from Gant to Gradle, using the wrapper. It all works fine for me but this afternoon one of my colleagues has had terrible problems. His ADSL line is fine, but the download of the wrapper zip file failed to work correctly on three occasions before it finally did complete. This is perhaps not a Gradle problem per se except . . .
The Gradle Wrapper code is making no checks concerning the validity of
the zip file before trying to open it. There is a fundamental
assumption that the zip has come across successfully so the user sees a
huge stack trace when it doesn't. Not the best UI for people using
Gradle who are not programmers.
I think the wrapper code needs extending so as to assume the zip
download fails as often as it succeeds. Failure should be notified to
the user and that person asked whether a retry should be undertaken, or
everything abandoned. I think this should be 5 mins work but . . .
Another comment is that 21MB is a huge amount to have to download -- is
there any way of making the required distribution smaller?
I do like the idea of a once per download download, so I don't think
doing download of parts on demand is appealing. The problem here is
disconnected working (of which I do quite a lot). Knowing that
everything I need is downloaded whenever a download is undertaken is
very reassuring. Nonetheless 21MB is a lot of download to have to wait
for, especially when it doesn't work.
Sadly this all left a bad taste in my colleagues mouth :-(
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
