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.
Summary: | CVS update of projects blocks other CVS functionality | ||
---|---|---|---|
Product: | versioncontrol | Reporter: | Antonin Nebuzelsky <anebuzelsky> |
Component: | CVS | Assignee: | issues@versioncontrol <issues> |
Status: | NEW --- | ||
Severity: | blocker | CC: | issues, jdinga, jrojcek, ttran |
Priority: | P2 | Keywords: | RELNOTE, USABILITY |
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Antonin Nebuzelsky
2005-10-19 17:00:38 UTC
I do not wish to infest the module with random bugs resulting from running concurrent CVS commands in the same workdir in this phase of development. We can take this discussion offline if you feel that making this possible really outwieghts such quality degradation. OK, but I'd like to note that this forces me to run CVS update externally. I cannot use it in the IDE. I will use only CVS module functionality which finishes quickly because I cannot wait 2 hours to be able to do diffs or see annotations. Trung, I think, it's your turn to decide if this should be fixed or not. I would recommend running huge updates of CVS repository externally anyway. If nothing else, you can schedule it to run at night. Also working with files and updating them at the same time is always risky. One thing is that one long running CVS task blocks the rest. This is something IMHO should be fixed but you may argue that the current state is as designed. Another thing is that when the user invokes Show Annotations action, the Loading Annotations task appears in the list of running background tasks, but in fact no loading of annotations is happening at all! User has no way to realize that Loading Annotations task is in fact Waiting 2 Hours For The Damned Update To Finish And Then Do My Job task. This is very bad and I don't think users will have an understanding for that. They will watch the task for 2 minutes, then they will become nervous and after 5 minutes they will start checking their network connection. After 10 minutes they will kill Netbeans and start WinCVS or whatever client they used before... ;) Changing back to DEFECT. At least the second part of the problem (see my last comment above) should be fixed. This can make users believe that performance of CVS actions is bad. Changing from P1 to P2, unless we agree that even the first part of the problem must be fixed (to have more queues for CVS commands). Why whould you want to kill Netbeans? We have this wonderful progress indication with cancel capability, right? You can abort the update if you need to. Anyway, I will NOT launch more than one CVS command over the same workdir unless I'm forced to, regardless of priority and issue type. OK, then users have to be warned about this behaviour. Letting them wait without any clue is bad. |