[GRADLE-1535] Tooling api should allow changing Gradle version / distribution in the wrapper Created: 12/May/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Kris De Volder Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

This is somewhat related to http://issues.gradle.org/browse/GRADLE-1533 (there's not much use implementing this improvement unlesss already implemented 1533)

I would like the IDE to be able to control what version of Gradle is being used by a project (so it would be like a project preference the user can set from within the IDE).
(Or for the IDE to override or offer fixing if version doesn't match what the IDE or tooling API expects).

See also https://issuetracker.springsource.com/browse/STS-1753

I can already do that, in a way, since the API does allow me to specify a distribution explicitly when opening a connection. However, this doesn't affect what
version will be used on the commandline. Also if that kind of "project specific preference" is to be persisted somewhere, I could certainly save it in some
Eclipse configuration file somehow but it would make Gradle on the commandline and inside the IDE behave differently (use different version of Gradle)

So... I'd would rather have some method on the tooling API that let's me set the distribution/version on a Gradle project in such a way that it gets persisted
in the project state, in a way that Gradle understands.

 Comments   
Comment by Adam Murdoch [ 12/May/11 ]

An excellent idea

Comment by Kris De Volder [ 12/May/11 ]

Of course, I guess I could probably just read and write the wrapper properties file myself.
But maybe its better not to... in case you guys decide to change the format

Comment by Adam Murdoch [ 12/May/11 ]

Let's do it through the tooling API. We certainly might change the format again.

In addition, changing the version might involve rebuilding the wrapper jar, as well as changing the properties file. Or hitting a server somewhere to figure out where the distribution is, or which distributions are available. Or preemptively downloading the distribution. Or translating the build script to the new version. Or ...

Comment by Kris De Volder [ 12/May/11 ]

Right. I certainly prefer to go through the API. I'd only consider the "hacky" approach if there's no other option.

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 11:57:58 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.