[GRADLE-3098] Weird line number reported when there is an unclosed brace syntax error in build.gradle Created: 02/Jun/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

Here is my build.gradle:

repositories {
}

{ And then when I run gradle, it report error as: FAILURE: Build failed with an exception. * Where: Build file '/v/arena/gradle/bug/wierd_line_num/trunk/src/build.gradle' line: 119 * What went wrong: Could not compile build file '/v/arena/gradle/bug/wierd_line_num/trunk/src/build.gradle'. > startup failed: build file '/v/arena/gradle/bug/wierd_line_num/trunk/src/build.gradle': 119: expecting '}

', found '' @ line 119, column 1.
1 error

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

It report the error is on line #119, which is apparently wrong, as my build.gradle has only 4 lines of code, I am using gradle (1.10)

Any idea?

Thanks.



 Comments   
Comment by Bartosz [ 27/Sep/15 ]

Is there some way to actually get the actual line number? I can't find my syntax error.

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 [ 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.

Generated at Wed Jun 30 12:39:54 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.