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.
It is very hard to find out, if parser is still scanning filesystems, or if MDR repository is already initialized with up-to-date data. API should be simple. For instance singleton class ParserManager with methods ParserManager getDefault() //returns instance of itself Collection getTasks() //returns List of Tasks waitParsingFinished() //waits till all scheduled Tasks finish and probably other methods like add/removeTask This is just a first idea. If you have better one, I will not object.
Rising priority. This is necessary for testing.
Or change implementation to start parsing synchronous with filesystems mounting.
Isn's the parsing process too much time consuming? I'm wondering what could happen, if I (currently in non-projectized IDE) mount the whole CVS repository, which even though it is not intended to be used for compilation/execution/debugging, it is being mounted automatically as to be used for these tasks, therefore I believe the parser would start the parsing process which could last for several minutes at least. What do you think?
Your question is rather general. Yes, parsing process is time consuming, but regardless of subject of this issue. Please file another PERFORMANCE issue, if you want.
clazz and java modules was changed so that filesystems are scanned synchronously. This should solve your problem.