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 50958 - Peculiar message from Fix Imports
Summary: Peculiar message from Fix Imports
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: Macintosh Mac OS X
: P3 blocker (vote)
Assignee: Daniel Prusa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-28 19:15 UTC by _ tboudreau
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ss (67.87 KB, image/png)
2004-10-28 19:15 UTC, _ tboudreau 		Details
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 _ tboudreau 2004-10-28 19:15:15 UTC 
Appears to be losing java.lang.* - see attached screen shot.  
Started seeing this in build 041017, and seeing it now in build 
041028.
Comment 1 _ tboudreau 2004-10-28 19:15:42 UTC 
Created attachment 18587 [details]
ss
Comment 2 Martin Matula 2004-10-29 08:56:05 UTC 
Is the file that you are invoking the FixAllImports action on in a
project, or is it a free-standing java file?
Comment 3 _ tboudreau 2004-10-29 13:46:28 UTC 
It is in a project.
Comment 4 _ tboudreau 2004-10-30 01:17:02 UTC 
More info:

I think whatever cache code completion uses is corrupted - I can't get completion anymore 
on things like java.lang.Class.  

One thing that is *very bad* is that now, if I press ctrl-alt-F, Fix Imports *deletes* imports 
that are good, but which it cannot recognize, making my class uncompilable.


I think I can trace this back to a single incident, several restarts ago:  I had a class like
public class Foo extends Component
(it imported java.awt.Component)

I added a J to make iit
public class Foo extends JComponent

an exception with the message "object was deleted" was thrown, and after that code 
completion was broken, and this behavior started (I experienced it once before, and 
deleted the mdr cache).

Hope that helps some...
Comment 5 ehucka 2005-01-11 13:30:42 UTC 
old target milestone, please re-evaluate
Comment 6 Jan Becicka 2005-01-14 15:36:51 UTC 
Dane, please look at it. Thanks.
Comment 7 Daniel Prusa 2005-01-26 15:35:10 UTC 
I cannot reproduce this bug based on the given description. I have not
also seen problems with Fix all imports of this kind in recent builds.
There were made several fixes related to storage stability and
IvalidObjectExceptions. I belive they can cover this case.
Closing as works for me, however, if you encounter it again, feel free
to reopen this issue.