BUILD FAILED is not the best message

Help/Discuss Declarative Gradle
1

I use Gradle for the following tasks in my project lifecycle:

  • Build the app
  • Compile the tests
  • Run the tests

Running tests is not the same as building the app. There are other tasks, such as code analysis or generating documentation, that also don’t fit under the “building” category. Each task has its own role and should be clearly communicated.

I believe Gradle should recognize these distinctions and display messages that reflect the specific task being performed. Displaying “Build Failed” when a test failed is misleading.
Clearer messaging would help developers understand the various tasks and troubleshoot issues more effectively.

2

I full-heartedly disagree.
All these tasks are tasks of the build you have at hand, that’s just the terminology.
“BUILD FAILED” also is just the final line, before that you have exact information which task failed and why.

If you want anything of that changed, complaining here is not helpful, this is mainly a community forum where users like me help other users.
But feel free to open a change request on GitHub with your request.
But I wouldn’t expect anything to happen about that to be hones, but the Gradle folks will let you know. :slight_smile: