[GRADLE-2712] Diagnostic message should be more informative Created: 20/Mar/13 Updated: 10/Feb/17 Resolved: 10/Feb/17
Consider the following build script:
I get such a stacktrace:
This is too unclear to understand what is wrong.
|Comment by Adam Murdoch [ 30/Apr/13 ]|
Are you running with one of the logging command-line options, such as -s or -d? You might see if the default output without these options solves your problem.
|Comment by Dmitry Dobrynin [ 01/May/13 ]|
Default output is
FAILURE: Build failed with an exception.
Though such a message is not a critical bug but obscure. Sure a message like 'You specified null as a dependency' is a little bit clearer.
|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.