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 24343 - Marking of parser errors is not always up-to-date
Summary: Marking of parser errors is not always up-to-date
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
: 25744 27737 (view as bug list)
Depends on: 45721
Blocks:
  Show dependency tree
 
Reported: 2002-06-03 15:53 UTC by Jan Becicka
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 Jan Becicka 2002-06-03 15:53:30 UTC 
[200206030100]

1. Create class A:
public class A extends B {
}
2. Error annotation appears, because class B is
not defined.
3. Create class B:
public class B {
}
5. class A is still underlined, even thought class
B is already defined.
Comment 1 Tomas Hurka 2002-06-05 11:36:16 UTC 
Fixed in trunk.
Comment 2 Jan Becicka 2002-06-27 10:56:21 UTC 
bug still lives in 200206260100
Comment 3 Marek Grummich 2002-07-22 10:08:51 UTC 
Set target milestone to TBD
Comment 4 Tomas Hurka 2002-08-13 18:44:09 UTC 
*** Issue 25744 has been marked as a duplicate of this issue. ***
Comment 5 Svata Dedic 2002-09-06 13:39:14 UTC 
A change made to the A class would trigger a reparse. It is annoying,
but reparsing all opened files after some change is made in some
editor window is very inefficient, so I would recommend to live with
the issue rather than have CPU on 100% all the time.
Comment 6 Jan Becicka 2002-11-07 13:22:01 UTC 
*** Issue 27737 has been marked as a duplicate of this issue. ***
Comment 7 Jan Becicka 2003-07-11 09:33:39 UTC 
Enhancement for JAVA_MDR
Comment 8 Jan Becicka 2005-10-12 14:49:41 UTC 
This issue was already fixed.