[GRADLE-817] help the build developer by listing available methods/properties Created: 09/Feb/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.8 |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Dierk Koenig | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Description |
|
When programming a build, one has to know what methods are availbable, e.g. subprojects { ... }
dependencies { ... }
mavenCentral()
It's all too easy to forget or misspell those names. The same is true for available properties. One approach would be to list those items in the documentation in a single place (at least for the known ones, not the tasks that are available as methods, of course). A second approach would be a method that lists them to stdout. Third, the --gui could lists those (beyond what it does for tasks). Best, of course, would be IDE-internal help. For IntellijIDEA, that could be done via gdsl. |
| Comments |
| 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:
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. |