I'm trying to use NB (beta1) to debug the jdk.  I
finally got some debugging functionality to work
(although platform setup ignores any but the first
source path), but the startup time for NB makes it
unusable for me.

In particular, after the initial startup, a dialog
pops up entitled "Scanning Project Classpaths" and
then proceeds to walk the classpath of the entire
jdk (I pointed it at my build workspace instead of
the standard jdk).

Maybe my situation is unusual (pointing it at a
build of the jdk, with class files instead of jar
files), but I don't think it would be unusual for
outside developers to point it at their own large
classes directories.

This process takes about a minute on my very fast
machine (P4 3.4 GHz, fast disk); I can't imagine
what this would take on a slower configuration.

I don't know what it is scanning the classpaths
for, so I don't know the proper workaround.  B ut
at the very least, there could be some setting
that specifies whether to rescan on startup or not
(if not, there could be a way to trigger the
rescan); forcing the slow full-scan startup by
default makes it unusable in this situation.