encountering a parse error with dep prevents goclipse builder from continuing

[GoogleCodeExporter]

encountering a parse error with dep prevents goclipse builder from continuing

[GoogleCodeExporter]

Hey Bill, thanks for the report.  Can you explain a bit more what you would 
like to see in this case?  I'm not sure what the right answer is.

Original comment by [email protected] on 5 Dec 2010 at 7:31

[GoogleCodeExporter]

Ending an import with "}" instead of ")" completely disables the builder 
because the "dep" program returns an unexpected result.  There is no indication 
in the source editor that there is a problem with the imports.  There is, 
however, an error in the Eclipse log, which I forgot to mention:

Error parsing dependencies: 
/private/bill/work2/.metadata/.go/linux/386/tools/dep completed with non-zero 
exit value (255)

After the error from dep, the plugin completely stops reporting errors; if you 
fix errors or produce new ones, the editor does not reflect that.  There is no 
indication that "}" is the problem.  If you change "}" to ")", the editor 
starts reporting errors and corrections properly.

My guess is that the builder is dying because of dep's exit value.  If this is 
the case, maybe the editor can at least display a red "x" indicate that there 
is a problem with the import block.

Original comment by [email protected] on 5 Dec 2010 at 8:06

[GoogleCodeExporter]

I committed a fix for this. It determines when there's a problem parsing the 
deps, and adds a marker at the problem line number.

Original comment by [email protected] on 7 Jun 2011 at 4:19

• Changed state: Fixed