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 45721 - classes/methods are marked as unknown if they were not saved yet
Summary: classes/methods are marked as unknown if they were not saved yet
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks: 24343
  Show dependency tree
 
Reported: 2004-06-30 10:22 UTC by hlein
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hlein 2004-06-30 10:22:34 UTC
Build 200406291800
In my project have some classes (everyone in a
separate .java file), e.g. o2eServerThread and
utils. In o2eServerThread there are calls to
methods in of utils. All these calls are marked
with a red cross at the left and the tooltip says:

cannot find symbol
symbol: variable utils

although all methods of the class utils are
declared public static.
Comment 1 ehucka 2004-07-12 10:08:30 UTC
Could you provide detailed description of this problem? Or attache
example code to reproduce it. Thank you.
Comment 2 hlein 2004-07-12 18:22:29 UTC
In the meantime I have cleared the cache in .netbeans and installed a
newer version of Netbeans. At the moment I cannot reproduce it myself.
I think that clearing the cache has something to do with it.

However, the check seems to be dependent on the compilation of a
class. I.e. there is a method m1 declared private in class A. In class
B of the same project you type A.m1() and you get the red cross at the
left and a tooltip message explaining the reason. This is correct. 
Then, you change the declaration of m1 in class A from private to
public (in the source, not recompiled yet). The red cross in class B
remains there. If you type new references to A.m1() in class B, they
get the error mark, too. The errors are cleared only after recompile
of class A.
This is reproduceable.

Regards

Comment 3 Martin Matula 2004-07-17 12:08:16 UTC
This is currently how it works. You need to save the file your other
file depends on. I.e., if you add a method to file A, you need to save
it before this method is visible to other files. I am changing this to
an enhancement request to be able to find out about the method even if
the source containing it is not saved yet.
Comment 4 Jan Becicka 2005-10-12 14:25:16 UTC
Already fixed.