[GRADLE-3196] Why Gradle download wrapper multiple times for the same version? Created: 18/Nov/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

In ~/.gradle/wrapper/dist/... for some Gradle/Wrapper versions I have multiple (2-7) "instances" downloaded (for the same version). Why Gradle cannot always use already downloaded instance for given version?

 Comments   
Comment by Gradle Forums [ 18/Nov/14 ]

Marcin, it is very easy with gradle to write task to clean duplicated wrapper's

Comment by Jochen Hinrichsen [ 20/Aug/15 ]

I wonder how that can be done. Probably depends on what's your meaning of 'clean'. If cleaning means to just remove duplicated versions from wrapper/dists folder, agreed, that's dead simple. But the installations will reappear whenever you start the gradle wrapper on the project that caused the installation, nay?

If cleaning means that no duplicate installations will reoccur, i wonder how that task will look like.

Comment by René Gröschke (Inactive) [ 20/Aug/15 ]

There could be two reasons for having multiple downloads for the same version.

1. You use different urls for resolving the same version(This might include different gradle versions (all vs bin.)
2. There was a change in the checksum calculation in the wrapper jar a while ago. This can cause multiple downloads. so if you have multiple gradle projects with different wrapper.jar files this can lead to multiple downloads for the exact same url.

I would vote for closing this issue.

Comment by Rafael Wolf de Goes [ 12/Feb/16 ]

Should Gradle wrapper also distinguish between http and https URLs for services.gradle.org/distributions/... ?

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:42:31 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.