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 97167 - Synchronization of dependent classes isn't occuring until class is active
Summary: Synchronization of dependent classes isn't occuring until class is active
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-04 07:34 UTC by John Baker
Modified: 2007-09-26 09:14 UTC (History)
2 users (show)

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 John Baker 2007-03-04 07:34:23 UTC 
I wasn't sure which category, seems to be a retouche issue:

There was a syntax error still appeared in one class even though it was resolved
in another class.  Not until, each class was made active in the Editor did the
red squiggly error mark go away.

(note: don't close any of the editor views for each file)
1) Create an interface IF1 with one method that has a parameter of type Class1
2) Create a class, Class2 that implements IF1
3) Implement the method from IF1 in Class2, but make the parameter type
incorrect (e.g. Class3.)
4) Fix IF1 by changing the parameter type of the method to Class3
5) Create Class3
6) Make Class2 active
note red squiggly line in the Class2 declaration (Class2 is not abstract,
doesn't implement ...)
7) Open IF1, note the red squiggly shows but quickly goes away
8) Switch back to Class2 
red squiggly again shows and quickly goes away.

It should not be required to make IF1 active in order to refresh Class2
Comment 1 Jiri Prox 2007-03-04 10:48:55 UTC 
Seems as duplicate of issue 92434 to me. jbaker can you, please verify, that
after typing any letter in Class2 the error will go away?
Comment 2 John Baker 2007-03-04 19:31:38 UTC 
It does appear to be a duplicate of 92434.

I will close but the priority of 92434 should be at least a P2, usability problem.

If 92434  the scenario I provided could be used to make sure the bug is fixed

*** This issue has been marked as a duplicate of 92434 ***
Comment 3 John Baker 2007-03-07 00:02:11 UTC 
I'm still seeing this even after typing a character and saving the file.
The module that contains the file clean-builds successfully, but the
file still has a red squiggly. 

I visited each of the dependent files and typed a character and saved
then returned to the file with the red squiggly - still shows.
Even compiling the file succeeds
Comment 4 Jan Becicka 2007-03-15 13:54:10 UTC 
Please attach build number. Thanks.
Comment 5 Jan Lahoda 2007-03-23 16:08:26 UTC 
I am not sure what is the relation between this issue and issues #56152 and
#92434, but lets investigate for 6.0.
Comment 6 Tomas Zezula 2007-08-31 17:36:48 UTC 
Not a duplicate of #92434, at least I think so.
Comment 7 Petr Hrebejk 2007-09-01 10:31:03 UTC 
Strange. This issue is reported against 5.0 but at the same time it says it seems to be retouche issue. Anyway I've
tried to reproduce this in the lates 6.0 build several times and I did not succeed. Feel free to reopen if you still
experience this problem.
Comment 8 Tomas Zezula 2007-09-02 08:11:32 UTC 
The reported case works for me too, but when you slightly change the stem number 5, by renaming some other class to
Class3 instead of creating it, it is reproduceable. Sorry
Comment 9 Jan Becicka 2007-09-19 13:55:41 UTC 
This feature does not exist in 6.0.