| Summary: | NPE logged as warning, error reporter does not pop up | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Ralf Sternberg <rsternberg> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | marcel.bruch, mateusz.matela, stephan.herrmann |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
|
Description
Ralf Sternberg
Ralf, by convention AERI (automated *error* reporting) does not respond to warnings. That explains why you don't get an error popup. This particular problem belongs to JDT UI I guess. Moving it there for triage. @Mateusz, do you think this qualifies as a duplicate of bug 475746? (In reply to Stephan Herrmann from comment #2) > @Mateusz, do you think this qualifies as a duplicate of bug 475746? Well, identical stack trace and matching time frame suggest that this particular exception will almost certainly not occur with newer builds. This bug report is more general though, isn't it? Ralf suggests that when a problem like that occurs in the formatter (or other components), the user should be able to send a report on it. I agree it may help catching more bugs. I've seen some automated reports for exceptions from the formatter, so I'm not sure why it's not the case here. Maybe it's because the formatting was called from ASTRewrite which decided that failure at this point is not important enough, or maybe something has changed recently in this context. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |