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 135894 - Background error parsing is not updated correctly
Summary: Background error parsing is not updated correctly
Status: RESOLVED DUPLICATE of bug 168237
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: Macintosh All
: P3 blocker (vote)
Assignee: Rastislav Komara
URL:
Keywords:
Depends on:
Blocks: 121950
  Show dependency tree
 
Reported: 2008-05-27 15:19 UTC by mikbra
Modified: 2009-08-06 08:40 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 mikbra 2008-05-27 15:19:52 UTC 
The background error parsing (the error signs in the margin in the editor) do not get updated if I update the source code outside the IDE, e.g. with external 
subversion tool etc. I'm using freeform projects a lot. I haven't experienced this problem in previous versions of netbeans.

Workaround:
1. Quit netbeans
2. Delete ~/.netbeans/6.1/var/cache
3. Start netbeans
Comment 1 Jan Becicka 2008-07-24 15:39:59 UTC 
Is the step 2. necessary?
Comment 2 mikbra 2008-08-19 06:58:53 UTC 
Yes, step 2 is necessary.
Comment 3 mikbra 2008-08-19 08:15:52 UTC 
Example scenario:

Class Foo uses the class Bar. Foo and Bar is modified outside the IDE (e.g. external svn, emacs, code-generation). When I return to the IDE where Foo is open 
it will mostly contain "compile errors" (e.g. if I added a new method in Bar and Foo uses that method). In my case Foo and Bar are located in different projects, 
not sure if it matters. The error is resolved if I open Bar in the Netbeans editor and then go open/activate Foo in the editor. If this happens to many classes at 
the same time I usually use the workaround in the first comment since it is too cumbersome to visit all files in Netbeans (in dependency order?).
Comment 4 mikbra 2008-08-19 08:15:53 UTC 
Example scenario:

Class Foo uses the class Bar. Foo and Bar is modified outside the IDE (e.g. external svn, emacs, code-generation). When I return to the IDE where Foo is open 
it will mostly contain "compile errors" (e.g. if I added a new method in Bar and Foo uses that method). In my case Foo and Bar are located in different projects, 
not sure if it matters. The error is resolved if I open Bar in the Netbeans editor and then go open/activate Foo in the editor. If this happens to many classes at 
the same time I usually use the workaround in the first comment since it is too cumbersome to visit all files in Netbeans (in dependency order?).
Comment 5 mikbra 2008-08-19 08:16:38 UTC 
Example scenario:

Class Foo uses the class Bar. Foo and Bar is modified outside the IDE (e.g. external svn, emacs, code-generation). When I return to the IDE where Foo is open 
it will mostly contain "compile errors" (e.g. if I added a new method in Bar and Foo uses that method). In my case Foo and Bar are located in different projects, 
not sure if it matters. The error is resolved if I open Bar in the Netbeans editor and then go open/activate Foo in the editor. If this happens to many classes at 
the same time I usually use the workaround in the first comment since it is too cumbersome to visit all files in Netbeans (in dependency order?).
Comment 6 Rastislav Komara 2009-02-03 10:52:43 UTC 
Overtake.
Comment 7 Dusan Balek 2009-08-06 08:40:29 UTC 
The problem with external modification is tracked by another higher priority issue.

*** This issue has been marked as a duplicate of 168237 ***