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 50877 - "Scanning Project Classpaths" loops when starting IDE
Summary: "Scanning Project Classpaths" loops when starting IDE
Status: RESOLVED WORKSFORME
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:
 
Reported: 2004-10-27 00:57 UTC by edbolson
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description edbolson 2004-10-27 00:57:05 UTC
If I have exited NetBeans with a project open,
then the next time I start NetBeans 4.0 beta 2,
the "Scanning Project Classpaths" dialog keeps
coming up  over and over.  In order to be able to
work, I must close the current project in between
the dialog appearances and then exit netBeans.  If
I start NetBeans without a project open, then open
the project, everything appears to work normally.

This is NOT the same as other scanning bugs that I
have read about, at least their descriptions don't
match.

One very important thing to note - my source and
project files are on a mounted share, from a Sun
PC Netlink server - this emulates a Windows NT
primary domain with a few enhancements that
support Windows 2000 and XP clients.

I suspect that there is a problem with comparing
times and/or dates, but cannot find out how to
verify that.

This is an extremely vexing problem, because I
can't leave my projects opened and in a consistent
state.
Comment 1 Jesse Glick 2004-10-29 15:12:13 UTC
No known steps to reproduce. I agree that some problem with timestamps
is the most likely explanation. Check to make sure your server and
client agree on the time (in UTC)!

Wrong component - if you are unsure of which component to use when
reporting a bug, please use 'ide'.
Comment 2 Martin Matula 2004-10-29 15:24:24 UTC
This does not relate to a timestamp checking. It is more likely a
problem with URL conversion. In the current build javacore is more
robust, detects ClassPath inconsistencies causing loops and throws
appropriate assertion errors. So, I believe this is fixed. But, could
you please verify that with the current daily build of NetBeans?
Comment 3 edbolson 2004-11-01 06:01:42 UTC
The client and server are time-synced
I most likely won't be able to test thi swith a new build for a couple
of weeksd due to an injury and a vaction. (not fun that the first
precedes the second!)
I
Comment 4 edbolson 2004-11-04 23:06:40 UTC
I downloaded daily build for Oct 31:
netbeans-4_0-daily-bin-200410311900-windows-31_Oct_2004_1900.exe

This version does not exhibit the problem.
I'm setting it to "WORKSFORME" - perhaps it should be "FIXED", but I
am still
unsure of who is supposed to set these things!

Comment 5 Quality Engineering 2007-09-20 12:03:12 UTC
Reorganization of java component