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.
I'm working with a CVS filesystem. I had a file which was modified locally, but another more urgent change needed to be committed. So I renamed the file in the Explorer tree; it showed it as Local and the original file reappeared with Needs Update status. So I did a CVS Update, then edited the file and committed the change. Having got that out the way I wanted to return to what I'd been working on. I duplicated the changes in my Local version, then deleted the Up-to-date copy (which returned to Needs Update status) and renamed the Local file back to its original filename. Unfortunately, I'm now left with two identically named nodes in the Explorer tree for the file, one with status "Needs Update; 1.51" and one with status "Locally Modified; 1.51". Doing a Refresh or Refresh Recursively in either the Project or Files views fails to remove the extra node. I tried performing an Update on the one which says it needs it, but that made no difference either. In the end, the only way I could find to return things to normal was to exit Netbeans and restart it.
During the reproduction of this I got a NPE (attached below). When I did the same steps with .txt files, all went O.K. and i ended up with one node for the file. Therefore the bad state seems to be caused by the exception.
Created attachment 19626 [details] The NPE.
Moving to java module.
*** This issue has been marked as a duplicate of 52975 ***