[GRADLE-3008] Wrapper install mechanism should recover from faulty/partial downloads Created: 25/Jan/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Host OS: Ubuntu Linux 13.10, linux kernel 3.13
SDK tools version: 22.3
Android Studio 0.4.3
Gradle plugin 1.10

1. Start a build of a (new) project requiring the download of a gradle-x.y-bin.zip package
2. For some reason the connection drops during the download, and the package is only partially downloaded (or maybe for some other reason the file is corrupted)
3. The connection is re-established

EXPECTED RESULTS: Gradle should recognize that the file is only partial (or maybe corrupted), and should download it again, or, better, restart the download from where it stopped

OBSERVED RESULTS: Gradle throws an IOException trying to extract the zip file, the build fails and there's no way to make it work again but manually removing the partial zip file.

Thank you for the great work!

Davide Natalini

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:37:24 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.