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 25543 - Some CVS status displaying incorrectly in Filesystems window
Summary: Some CVS status displaying incorrectly in Filesystems window
Status: CLOSED DUPLICATE of bug 25364
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscvs (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-11 16:09 UTC by Steven Ostrowski
Modified: 2002-07-12 16:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Ostrowski 2002-07-11 16:09:04 UTC
A couple of my files are displaying the incorrect
status in the Filesystems window. For example, I
have a file that is in CVS but the IDE displays it
as local. When I try to do a CVS add (the IDE lets
me do this since it thinks it is local), CVS
responds with the error message that it is already
in the repository.

This has happened to a couple of files, and has
also happened where the IDE displays as if the
file is locally modified but if you check the real
cvs status it is up to date.

This can be confusing and unfortunately there's no
error log to attach, it's only a display thing.
Comment 1 Jiri Kovalsky 2002-07-12 08:01:24 UTC
Does manual refreshing help ? This seems to be pretty similar to issue
#25364.
Comment 2 Steven Ostrowski 2002-07-12 16:14:35 UTC
I don't see an option for manual refreshing. If you are referring to
re-opening the filesystem folder, yes I tried that and it did not fix
it. It also was not fixed if I restarted Netbeans.
Comment 3 Jiri Kovalsky 2002-07-12 16:23:02 UTC
No, I mean right clicking the root node of your CVS filesystem and
choosing "CVS|Refresh Recursively" from the popup menu. Can you try it ?
Comment 4 Steven Ostrowski 2002-07-12 16:27:53 UTC
Ok, YES that "fixed" it. Hope that gives you enough information to fix
it in the next release!

Thanks
Comment 5 Jiri Kovalsky 2002-07-12 16:31:23 UTC
Okay, in such case resolving this as duplicate of issue #25364. Thanks
Steven for this information !

*** This issue has been marked as a duplicate of 25364 ***
Comment 6 Steven Ostrowski 2002-07-12 16:36:11 UTC
I'm not sure this is a duplicate of that issue, but I trust your
better judgment =) In my case, this was only happening on a couple of
files out of many. It sounds like with the other issue it was
happening on all files in a directory where there was a subdirectory.