Bugzilla – Full Text Bug Listing
| Summary: | Compiler's "Internal error" box is broken | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Johan Walles <johan.walles> |
| Component: | UI | Assignee: | Kevin Haaland <Kevin_Haaland> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | magnus.ihse.bursie |
| Version: | 2.0 | Keywords: | usability |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
This should be a standard platform UI mechanism. Moving to platform |
What happens time and time again in the eclipse ng is that: * The compiler breaks for somebody * They get an entirely uninformative error message like "Errors during build: org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding" (real world example) * They post a "what happened?" message to the ng. * Somebody tells them about the .metadata/.log file * Actual error reporting begins in the ng * A bugzilla entry may get posted at some later time With a better error box, this could be shortened into: * The compiler breaks for somebody * They report it into Bugzilla (unless it has already been reported) The error box could be improved by including: * a pointer to the log file ("For more information, have a look in /complete/path/to/the/workspace/.metadata/.log") * an option to view the contents of that file (like a "More >>" button that would add a text box with the contents of the log file) * something about how to look for similar bugs in Bugzilla ("You can see if this is a known problem by searching our Bugzilla at http://dev.eclipse.org/bugs") * something about filing new bugs in Bugzilla ("If there is no bug report about this already, please file one at http://dev.eclipse.org/bugs/enter_bug.cgi"). I don't know enough about Eclipse to tell whether this is an Eclipse core issue or a JDT issue, but it *is* an issue and it should be fixed.