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 have a link in the project view to a sourcetree. The sourcetree from a node in a cvs filesystem. When i commit a file in the project view tab it does not update the 'special text' after the file name. For example is still says "Locally Modified, 1.11", however if i switch to the filesystems view the special text is "Up-to-date, 1.12", then when i switch back to the project view it is then updated to say "up-to-date v1.12".
build 20
Well, I have to say that I can't reproduce it here. I have file added to Project Default that is [Locally Modified, 1.1]. If I do "CVS|Commit" on such a file its status is changed to [Up-to-date, 1.2]. So please provide us with more information of how to reproduce it otherwise we will have to resolve it as WORKSFORME. I mean the detailed step-by-step procedu- re like: 1. Mount CVS filesystem 2. Create [Local] file 3. Add it to project 4. "CVS|Add" -> [Locally Added, New] 5. "CVS|Commit" -> "Up-to-date, 1.0]
this bug seams to be inconsistant. I just rebooted my box and it appears as though i can't reproduce it. However i went to another engineers box and he was able to reproduce it straight away. He leaves netbeans running for days (if it will let him). even when this bug does occur, it seams to update 'after a while', which makes me wonder if perhaps a background thread is getting a bit bogged down or lazy at updating. I tried to come up with a better set of steps (starting from "mount cvs filesystem") but i couldn't get the problem to occur. So here's the best i can do (from my buddies box): 0: cvs filesystem already setup: working dir set to whatever, no realive mount point, pserver, etc. Using cvs exe that comes with the dl of wincvs1.1 (or whatever the latest version is). 1: select the project tab (if not already selected) 2: open the source file you wish to commit and open with the sourceeditor 3: modify the file 4: save the file by hitting control-S 5: in project view rt click on the file and select cvs->update 6: once completed, and no merge conflicts, rt click on the file and select cvs- >commit 7: enter your comment and hit ok The status bar then says Command Commit_CMD is running. The status bar then says Command Refresh finished. Review the file in the project view and tabbar in the source editor. Notice that it has not changed. Then hit the filesystems tab and navigate to the file and review if it has changed, and i have found that it has changed to "up-to- date, X.xx"
*** Issue 11057 has been marked as a duplicate of this issue. ***
[NB32-22] jdk1.3, rh70 ============= Martin, I was able to reproduce it as Peter describe on #22 Reproduction was easy for me. I didn't have running ide for days but only for 2 hours.:) I 've done commit via popup menu from the editor (7:) and waited utill the commands in status bar didn't finished: Command Commit_CMD is running. Command Refresh finished. Nothing was change: all 3 statuses of file (Title of Editor, Tab of the Editor and Explorer->Project Tab) left unchanged [Locally Modified, 1.12] When I switched to FS Tab in Explorer the status was old too:-( Not even manualy invoked Refresh could help:-(((( Just only Revision Explorer was able to display that revision 1.13 exists. See attachments (snapshot, command outputs)
Created attachment 1029 [details] Screenshot of invalid Statuses
sorry, but I've lost my command outputs:-( and I'm not able to reproduce it again. Maybe it depends on ide's running time:-/ Maybe the priority could be lowered (because of hard reproduction)?
CVS module fires correctly the annotation changes. There can be some bug in listeners in projects or editor support. Since the bug is probably somewhere outside of vcscvs module, changing the product to openide.
The problem will probably lie in DataNode.
Created attachment 1032 [details] Another inconsistency in Editor title and tab name !
Created attachment 1066 [details] datanode_patch.jar
I cannot reproduce this bug. IMO DataNode correctly fires changes after FileSystemEvent call. So I attached patch, which prints process of this firing: DataNode gets annotationChanged event DataNode calls Node.fireDisplayNameChange Can somebody use this patch to localize bug cause?
Resolved for 3.4.x or earlier, no new info since then -> verified
Resolved for 3.4.x or earlier, no new info since then -> closing.