[GRADLE-1741] Expose remotely available gradle versions via the tooling api Created: 11/Aug/11  Updated: 16/Jan/17  Resolved: 16/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-4
Fix Version/s: None

Type: New Feature
Reporter: Denis Zhdanov Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Consider the situation when end-user works with the gradle via application, which in turn uses tooling api. It seems convenient to allow end-user to choose target gradle version to work with. The actions sequence looks like below then:

  1. Intermediate application asks the tooling api about remotely available gradle versions;
  2. The application shows GUI with the available versions to the end-user;
  3. End-user selects target gradle version he or she wants to work with;
  4. The application downloads target version (GradleConnector.useDistribution());

 Comments   
Comment by Mark Vieira (Inactive) [ 12/Feb/16 ]

Not sure this is something that should be added to the Tooling API since there is a service endpoint you can hit to gather this information: http://services.gradle.org/versions/all.

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 [ 16/Jan/17 ]

From my perspective it should be easy enough to hit the URL provided by Mark to retrieve available version. We are not going to build that functionality into the Tooling API.

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