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 47716 - User is allowed to work with UI for a while before scanning project classpaths finishes
Summary: User is allowed to work with UI for a while before scanning project classpath...
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-08-23 15:26 UTC by Antonin Nebuzelsky
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot (106.68 KB, image/png)
2004-08-23 15:27 UTC, Antonin Nebuzelsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2004-08-23 15:26:38 UTC
Scanning project classpaths should happen
immediately after the IDE starts and only after it
finishes completely user should be able to start
working with the IDE. I encountered several times
that part of the scanning is done, then the
progress dialog disappears, I am allowed to start
working with the IDE and then suddently the
scanning continues.

See the attached screenshot. I opened Go To Class
dialog when it seemed that the scanning is over
and all of a sudden it appeared again and continued.
Comment 1 Antonin Nebuzelsky 2004-08-23 15:27:13 UTC
Created attachment 17034 [details]
Screenshot
Comment 2 Martin Matula 2004-09-23 13:18:37 UTC
I have not been able to reproduce this and I've never seen this when
doing the usual work in the IDE since the time this bug was reported.
Tondo, could you provide more info on what you did? Since this is so
hardly reproducible and it does not seem to cause any damange even
when it occured to Tonda, I am lowering the priority and will close
this issue as works for me if no other information is provided in say
2 weeks timeframe.
Comment 3 Antonin Nebuzelsky 2004-09-24 10:04:13 UTC
Well, what else can I say? I think I described the situation completely.

Anyway, I did not see this for some time either. Feel free to close it
as fixed. I'll reopen it if I encounter it again.
Comment 4 Martin Matula 2004-10-26 15:59:14 UTC
I was not able to reproduce this for a long time now. Anyway, scanning
can now happen even during normal editing if some of the files on the
classpath (e.g. a jar file that is a product of the project build) is
changed.