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.

Bug 35032 - Explorer node and source editor tab have parse error, but non in file
Summary: Explorer node and source editor tab have parse error, but non in file
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: -S1S-
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-21 20:17 UTC by ssffleming
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ssffleming 2003-07-21 20:17:27 UTC 
I was refactoring code with a group of files
and had an incorrect package name at the top of a java
source file.  I corrected the package and recompiled
the file using the compile context menu action in
the explorer tree.  The red error tag was not removed
correctly and it indicated a parsing error.  Looking at the 
file in the source editor showed there were no longer
any parsing errors (No red in the source file text display)
showed now
Comment 1 ssffleming 2003-07-21 20:18:56 UTC 
I cleared the problem by shutting down and restarting
the IDE.  Closing and reopening the source file still
would not produce any parsing errors.
Comment 2 Martin Roskanin 2003-08-08 14:38:14 UTC 
Yes, the synchronization between parser and explorer is somehow broken.
I have reproduced the similar problem:
1. make an error in code
2. immediatelly press F9 to compile.
3. error is highlighted in editor glyph and explorer node. This is
correct behavior.

Incorrect behaviour:
1. make an error
2. wait 2 seconds for background parsing to annotate the error in
editor glyph gutter
3. press F9 to compile
4. explorer node is not highlighting the error.

I am not sure where this issue belongs, trying java module...
Comment 3 Martin Matula 2004-07-28 12:50:57 UTC 
Parse error indication on whole file was dropped.