On 6/29/2010 4:29 AM, Jan Goyvaerts wrote:
Project scanning ! Tor mentioned this can be disabled. But really... why it is scanning the very same Maven libraries each time I'm starting up ? NB takes a kickass start and stamps right away onto the breaks as soon as it is scanning the tenths of Maven libraries my projects have. I thought Maven libraries are by their nature immutable. They're cast in stone once they get a final version. So why am I seeing each morning the same lengthy procession of scans ? Usually when I'm - trying - to show off Netbeans to my colleagues. :-)
First off, I have to say that the scan on demand feature did *not* work for me in 6.9. I read the Wiki page on it and nothing seemed to work as advertised.

Secondly, I've griped about project scanning since about NetBeans 4.0 and it's still a problem. It should be faster and start less often. That said, those behaviors could be ignored as long as it didn't consume *too* much CPU and disk while running in the background and, above all, didn't stop you from doing things. By this I mean that if you're doing Go-To-Type and NetBeans has once scanned the type you're looking for it should have no issue doing so again during scanning -- period. Even if it is rescanning the source tree containing that type, the old data should be available the entire time except for an atomic switch between the old and new scan data for the given source file. As it is now there are large periods of time where Go-To-Type (and many other functionalities) are not usable. Also there's the matter that Go-To-Type is still a lot slower than I'd expect for exact searches. I wrote a static analyzer using NetBeans' classfile module to index to a relational database, and slapped a web app on top of this. It finds types all but instantaneously. NetBeans thinks for quite some time in many cases.

--
Jess Holle

--
You received this message because you are subscribed to the Google Groups "The Java 
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to