[GRADLE-627] Gradle gives poor message for no build.gradle Created: 09/Sep/09 Updated: 24/Jan/17 Resolved: 24/Jan/17
When Gradle is started in a directory with no build.gradle file, the somewhat unhelpful message below is given. I think the situation where the file is not found should be handled specially so as to give a very specific error message.
|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 [ 24/Jan/17 ]|
Gradle now automatically invokes the help task which renders information about the command line usage.