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.
[ BUILD # : 200905140201 ] [ JDK VERSION : 1.6.* ] I have some opened files from an opened project and when I start IDE, the scan doesn't starts and the files are not parsed so, several errors are shown.
Until build 200905120201 everything works fine.
Here, I have freeform project and the workarounds I use are close and reopen the project or open Window > Tasks.
Another strange behaviour... :( If I add -J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE at netbeans.conf the scan is always executed... if I remove it, the scan doesn't run again at startup.
Just to clarify the last post, not always, but at most of times the scan is executed when I change the parameter... no idea why... probably just an coincidence.
I'm quite positive that the scan always starts. What you see is most likely a problem that some tasks run even before the initial scan. Typically these tasks are launched from ProjectOpenedHook and since the initial scan waits for all projects to get opened any task launched from ProjectOpenHook (even if launched through ParserManager.parseWhenScanFinished()) will run before the initial scan. I'll fix that.
Vita, I don't agree with new subject. Another errors are that Go to Type doesn't work too as well if I open any file from Projects view. Anything that need indexes doesn't work until scan is started at least once. Regards
"Anything that need indexes doesn't work until scan is started at least once" - Correct. I think I know why that is so. I filed issue #165245 to cover this problem.
This should now behave better - http://hg.netbeans.org/jet-main/rev/6a59b3dc1388. There are still many problems with badges, see issue #121950. The roots of these problems lie back in Nb6.0 and there is no simple solution for them. We will try to do a bit of an overhaul of this part in 6.8, but for 6.7 this is simply as good as it is. I'm sorry.
Integrated into 'main-golden', will be available in build *200905171401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/6a59b3dc1388 User: Vita Stejskal <vstejskal@netbeans.org> Log: #165170: block TaskProcessor after the IDE start until the projects are open
Just for the record, this is a related changeset - http://hg.netbeans.org/jet-main/rev/0c0c5e853b3d
Now, it is worst than before. Now, when I open the IDE, files are not parsed, so, no code folding available as well Go to Type doesn't work too. And, after several seconds (almost one minute), files are parsed and everything in file is broken (no files can be compiled by editor). And, even I start Tasks for example, nothing change. So, I just can't use this build. Product Version: NetBeans IDE Dev (Build 200905180201) Java: 1.6.0_11; Java HotSpot(TM) Client VM 11.0-b16 System: Linux version 2.6.27-14-generic running on i386; ISO-8859-1; en_US (nb) Userdir: /home/hmichel/.netbeans/dev
O increased the priority since now there is no workaround and the latest build is unusable. I switched to 200905151401.
Ok, I reverted 6a59b3dc1388. http://hg.netbeans.org/jet-main/rev/9bfb851c4619
"when I start IDE, the scan doesn't starts" - I think I found the way how to replicate this (at least sometimes). If there are only a few projects and they open really fast. Sometimes they are opened even before the indexing is initialized and so the initial set of events about new classpath registered from the projects don't arrive.
I have 2 hudson repositories added to Hudson support. I can see that this job always run, and when the 'Scanning projects' run, is always after (at least it is what seen to me) hudson stops. BTW, I have just one huge project opened at the time (I can reproduce it with more than one too) and some source files too (3 or 4). I will try to test a little bit more and get more details to you. If you need any log or someting else, just let me know.
BTW, I can't reproduce it anymore for build 200905190201. If I try with build 200905180201, nothing works and for build 200905151401, sometimes I need to open Tasks to force rescan. I will continue to test it the latest build and confirm that the problem doesn't exists more for me. For all tests, I've used the same userdir. Product Version: NetBeans IDE Dev (Build 200905190201) Java: 1.6.0_11; Java HotSpot(TM) Client VM 11.0-b16 System: Linux version 2.6.27-14-generic running on i386; ISO-8859-1; en_US (nb)
Ok, here is another attempt to fix this - http://hg.netbeans.org/jet-main/rev/fe24cebec2fe. The indexing is now initialized as soon as the parsing.api module is loaded, which ought to be before the IDE starts opening projects. That way we should not miss any events from GlobalPathRegistry and correctly pick up all classpaths registered from the projects. The initial scan is now also started when editors are opened, which apparently happens in no relation to opening projects. I think this was the main reason for editors showing errors after starting the IDE. The files were open, but their projects were not and so there was no classpath, etc available for the files. Unfortunately the indexing blocks other editor background tasks like semantic highlighting, code folds, etc, which are therefore unavailable until the initial scan is done. I'm not sure if I'll be able to do something about it. So far it looks like that we can either let the background tasks run and have a good chance of having the files opened in the editor marked with errors or we block the background tasks and have no code folds, semantic coloring, etc. Please try the fix and let me know.
Ok, after several tests, I can reproduce the problem. Many times I restart the IDE, it opens without run the scan, so the opened source files has compilation errors and another problems I talked before.
I will test your fix as soon as the build is available.
Thanks and sorry for the delay, the fix caused some commit-validation tests to fail (ie. because of several unexpected classes loaded on too early during the startup). Anyway, I fixed that and so the changes should propagate to today's build. I'll keep an eye on it.
Integrated into 'main-golden', will be available in build *200905210201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/fe24cebec2fe User: Vita Stejskal <vstejskal@netbeans.org> Log: #165170: initializing RepositoryUpdater as soon as possible; forcing initial scan from editor registry events
Ok, this should be now fixed.
Looks fixed to me too. Testing for feel days and the problem doesn't happen again. Thanks. v. 200905250201