[GRADLE-1372] Make the wrapper a build-in task Created: 05/Feb/11  Updated: 01/May/13  Resolved: 01/May/13

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.7-rc-1

Type: Improvement
Reporter: Hans Dockter Assignee: Unassigned
Resolution: Fixed Votes: 4


 Description   

What about making the wrapper a build-in task? It does not make much sense to configure it in the build script anyhow. The proposed way to maintain the wrapper configuration is via the properties file. I find it awkward and confusing at the moment, that initially you are supposed to configure in the build script and afterwards in the properties file.

So why not just make it build-in. Every property is generated with a default value. For customization and maintenance you just edit the properties file.

 Comments   
Comment by Nathan Neff [ 28/Mar/11 ]

Hello,

Jeff and I have a potential solution for this issue.
I will be submitting a pull request today (03/28/2011) or
tomorrow.

Thanks,
--Nate

Comment by Nathan Neff [ 30/Mar/11 ]

I also think that command-line switches would be nice when
calling "gradle wrapper", instead of editing the properties file.

For example, I have open-source project, and want to make it easy to run
gradle tasks, but I have a different distributionUrl. I could just say:

>gradle wrapper --distributionUrl=http://example.com/mygradle.zip

Comment by Szczepan Faber [ 09/May/11 ]

>What about making the wrapper a build-in task?

+1. It feels a bit weird to first change the version in script, then run the build. Much more natural would be to simply change the properties file and that's it. It is also a bit confusing that you can have version X in wrapper task in build.gradle but version Y in gradle-wrapper.properties.

Generated at Wed Jun 30 11:53:52 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.