Come on guys. There a numerous people complaining about the project scanning issues.
Here is one movie (
http://www.netbeans.org/nonav/issues/showattachment.cgi/83834/200906180201.ogg) showing the performance regression between 6.5 and 6.7
Just from today's nbusers emails
>
> I am trying disparately to be able to, once again, use a project which has had an unfixable "The project XXXXX has a broken platform reference. You have to fix the broken reference and invoke the action again." error. While trying to use 6.7rc3, starting from scratch, I encountered a lock up of the ide while exiting. I've created the issue at
>
> <
http://www.netbeans.org/issues/show_bug.cgi?id=167623>
>
> which illustrates the fact that the IDE, seemingly all over the place, is calling into the scanning/indexing code with the AWT-EDT and being blocked by bugs and implementation details of the prolonged locking associated with the cache implementation.
>
> Please vote for this one too so that we can, hopefully get enough documented issues to help the dev team understand the impact of this issue.
>
> Gregg Wonderly
>
and another
>
> Has anyone else noticed this on the recent builds: I'm in the IDE and have a few source tabs in the editor with one active and the methods/fields showing in the Navigator. I do something in the IDE outside the editor window (e.g. do a search or something) and then subsequently double-click on a method in the navigator that is supposed to take me to that method in the currently active editor window. Only it doesn't. Instead, the editor tab seems to "wake up" and refresh the navigator window. If I double-click on the method again, things work again.
>
> I can't reproduce this on demand - either it's occasional or is a sequence I haven't pinned down yet. Because of that, I hesitate to open an issue.
>
> Thnx,
> tom
>
