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 # : abf8e4eac4aa ] [ JDK VERSION : 1.6.* ] Time after time modified/new files vcs indication (different colors/badges) is not shown or even the refresh is really slow which makes it go away and back after some seconds. Sometimes the colors change from blue (changed) to black and so back to blue after some seconds, as well it happens with files/packages badges too. It looks like the vcs refresh is really slower now in 6.9.
vcs refresh is actually as fast as in 6.8 but annotations (badges and file colors) are calculated asynchronously so the AWT is not blocked and expanding of nodes is as fast as possible. The limitation of this better responsiveness is more frequent repainting of the annotations. Basically versioning returns an annotation that is currently available (in cache) and asks svn/cvs/hg status for the real annotation. When that value is available, nodes in projects/files/... views are repainted (that's why it sometimes happens that the nodes change from blue to black to blue). If you want to return back to the old implementation, you can start IDE with -J-Dversioning.asyncAnnotator=false But be aware that expanding of nodes will become much slower and the AWT will occassionally get stuck. The new behaviour is the fix for bug 171410. Closing this as WONTFIX, since we really have no intention to fix this (use the switch if necessary).
The problem is this cache seems to be broken. For instance, if a file is already marked as modified and I commit another file under the same versioning root, the modified file gets black first and then gets blue again. This makes no sense, even according to your explanation.
I am aware of one case when this happens. Committing a file makes all its parents (parent folders, packages, etc.) turn black and then blue again (if you have another file as modified). But i am not aware that another file gets repainted. I'll try your test case several times then.
I am using CVS.
Well, I can reproduce it with 'Select in Projects', 'Select in Files', many times just opening the Projects view it happens.
fix: http://hg.netbeans.org/cdev/rev/71f7c0058c3f
fix: http://hg.netbeans.org/cdev/rev/4f5af4c53201
misterm: after a commit, all annotations were refreshed (only in CVS), this should be fixed with http://hg.netbeans.org/cdev/rev/4f5af4c53201 - now only parents of a committed file change from blue to black to blue again - this cannot be evaded hmichel: items in the cache are kept only for a certain amount of time (i.e. 1 minute as default), with http://hg.netbeans.org/cdev/rev/71f7c0058c3f the max age is increased to 10 minutes. After the time limit the value is purged from the cache. For you two i suggest starting IDE with -J-Dversioning.annotator.cacheItem.maxAge=-1, this way the values won't ever get old and will be kept forever. The cache is also size-limited, so please experiment with -J-Dversioning.annotator.cacheSize=NUMBER_VALUE (the default is 500, you can increase the value and thus keep more annotations at the same time). Hope these will help...
Integrated into 'main-golden', will be available in build *201004090201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/71f7c0058c3f User: Ondrej Vrabec <ovrabec@netbeans.org> Log: Issue #183667 - [69cat] Time after time modified/new files indicator is not shown increasing the default value of the max age for cache items