This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Parser should ignore invalid source | ||
|---|---|---|---|
| Product: | java | Reporter: | Jan Becicka <jbecicka> |
| Component: | Unsupported | Assignee: | issues@java <issues> |
| Status: | CLOSED FIXED | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 3.x | ||
| Hardware: | PC | ||
| OS: | Windows ME/2000 | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | StackTrace | ||
Created attachment 632 [details]
StackTrace
I disagree. In fact, the explorer could easily display complete errorenous source, if there's enough support from Java Hierarchy APIs. The bug was most probably fixed during today -- I discovered some bad things in model implementation. [010220_1] Verified Resolved for 3.4.x or earlier, no new info since then -> closing. |
[dev-128] Let's have this invalid class: public class Foo { int field; int field; } In Explorer select "field" (there are two "field"s in Explorer as in source) and delete it. Exceptions are thrown. Source hierarchy shows only Error node.