[GRADLE-627] Gradle gives poor message for no build.gradle Created: 09/Sep/09  Updated: 24/Jan/17  Resolved: 24/Jan/17

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

Type: Bug
Reporter: Russel Winder Assignee: Unassigned
Resolution: Fixed Votes: 0


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.

> gradle

FAILURE: Could not determine which tasks to execute.

  • What went wrong:
    No tasks have been specified and root project 'russel' has not defined any default tasks.
  • Try:
    Run with -t to get a list of available tasks.


Total time: 1.436 secs


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

Gradle now automatically invokes the help task which renders information about the command line usage.

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