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.
Product Version = NetBeans IDE Dev (Build 200401251900) Operating System = Linux version 2.4.20-18.9 running on i386 Java; VM; Vendor = 1.4.2; Java HotSpot(TM) Client VM 1.4.2-b28; Sun Microsystems Inc. Java Home = /usr/local/java/j2sdk1.4.2/jre System Locale; Encod. = cs_CZ; ISO-8859-2 Home Dir; Current Dir = /usr/local/home/delphym; /usr/local/forte/forte3/NBdev-last/netbeans/bin IDE Install; User Dir = /usr/local/home/delphym/NBdev-last; /usr/local/home/delphym/.netbeans/dev ------------------------------------------------------------------------------- It's not nice thet for having all info up-to-date you must run more similar commands on the files instead running only one. Reproduction: ============== 1. have mounted 2 CVS FS: the same pserver/repo and different working 2. perform checkout on each FS to have the same content in them. 3. Modify a file "A" in the first FS and commit it 4. Invoke cvs-Status on the file "A" in the 2.FS 5. In the Status output you've got info about its Status, Working a Repo revision, eg.: wr:1.2, rp:1.3, Status [Needs Patch] but in the Explorer I have still this old info: [Up-to-date; 1.2] That's bad :-( once I've got some actual info about some file, why they are not kept and treated more effectively... I have run cvs-Refresh for the same file again :-(
Network bandwitch and duplicate task, user can't focus for some other task comfortably... Those are bad points which makes me fill it should be fixed in NB 3.6
This behavior is there from the beginning. Status command is independent and does not refresh the cached status information. Therefore this is more like an enhancement for the Status command behavior. Scheduling for 3.6 for now, if there will be time, we can try to implement this.
You're right, it's there from the begining... ITOH we can't call it as good integration, can we? I hope you'll find a time for this fix. Thanks
This would need severe enhancements in the Status command. This is on an edge between a defect and an enhancement. Scheduling for promo-D, we've already entered high-resistance mode.
This is more like an enhancement. Downgrading to P4, this is not a bug per se, it was not implemented.
Possible integration point StatusInfoPanel.setData() can ask FAQ for recent value and merge it updated info and FAQ.writeAttribute() it back.
FIXED in CvsStatusVisualizer.java new revision: 1.15