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: | Explorer tree confused with error in code | ||
---|---|---|---|
Product: | java | Reporter: | Milan Kubec <mkubec> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | screenshot |
Description
Milan Kubec
2005-09-26 09:26:00 UTC
Created attachment 25160 [details]
screenshot
P4 - just "cosmetic" bug. We hardly can display correct source tree for broken source. Well, then why do you update the tree in Explorer if source is broken. The tree was OK, then I did the error in source and the tree in Explorer was updated to the wrong state. I would suppose that if you detect an error in source code you won't update the tree, othervise it'd show wrong information. Nodes were removed from explorer. |