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 51532 - VSS: Statuses of nodes are not refreshed after VSS actions.
Summary: VSS: Statuses of nodes are not refreshed after VSS actions.
Status: CLOSED DUPLICATE of bug 50211
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcsgeneric (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-15 18:53 UTC by Peter Pis
Modified: 2006-03-24 12:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Pis 2004-11-15 18:53:51 UTC 
build NB 0411112107, turboCacheON

You can invoke e.g. "VSS | Add", "VSS | Create
Project", ... and after actions finish, statuses
are not refreshed. But in Runtime tab there is
record of refresh action that was successful.
Comment 1 _ pkuzel 2004-11-16 13:57:30 UTC 
Sounds like missing listener. In UserCommandSupport? Not sure. Anyway
TurboUtil.dirReaderListener is here to cactch it.

Martin suggested CommandProcessor.addCommandProcessorListener(). Cast
cmd parameter to VcsDescribed command and attach
TurboUtil.dirReaderListener.
Comment 2 _ pkuzel 2004-12-06 16:02:32 UTC 
I can see in trunk version too. 

However my config/vss.xml differs from Martins which defines refresh
policy.
Comment 3 _ pkuzel 2004-12-06 17:23:15 UTC 
Having correct vss.xml the problem does not exist anymore.
Comment 4 Peter Pis 2005-02-04 08:32:06 UTC 
Reopen.

Steps:
1. Register VSS versioned directory. 
2. Check out some project and create in it new package e.g "aa.bb".
3. Switch to Versioning view, select "aa.bb" package and invoke "Add
All". (Check "Add files recursively"). Push "OK" button.

Command finishes, but status changes only for the node that the action
is invoked.
Comment 5 Martin Entlicher 2005-02-10 10:02:44 UTC 

*** This issue has been marked as a duplicate of 50211 ***
Comment 6 Peter Pis 2005-06-16 16:45:11 UTC 
Verified.