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.

Bug 53132 - Duplicate explorer node after rename
Summary: Duplicate explorer node after rename
Status: RESOLVED DUPLICATE of bug 52975
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-08 00:17 UTC by ats37
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The NPE. (3.87 KB, text/plain)
2005-01-11 17:22 UTC, Martin Entlicher
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ats37 2005-01-08 00:17:24 UTC
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.
Comment 1 Martin Entlicher 2005-01-11 17:22:02 UTC
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.
Comment 2 Martin Entlicher 2005-01-11 17:22:39 UTC
Created attachment 19626 [details]
The NPE.
Comment 3 Martin Entlicher 2005-01-11 17:23:56 UTC
Moving to java module.
Comment 4 Jan Becicka 2005-01-14 15:18:11 UTC

*** This issue has been marked as a duplicate of 52975 ***