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 7387 - Thread doing checkout stays running after the user clicks "<Previous" button in the CVS wizard
Summary: Thread doing checkout stays running after the user clicks "<Previous" button ...
Status: CLOSED INVALID
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscvs (show other bugs)
Version: 3.x
Hardware: All All
: P4 normal (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-08-15 10:45 UTC by Antonin Nebuzelsky
Modified: 2003-07-02 17:17 UTC (History)
1 user (show)

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 Antonin Nebuzelsky 2000-08-15 10:45:55 UTC
To reproduce:

1) In the New CVS filesystem wizard get to the point where Check Out Module
radio button with the list of available modules is displayed

2) Select a module from the list

3) Click "Next>"

4) "Please wait, checkout in progress" appears and Forte is performing the
checkout of the module

5) Click "<Previous"

6) You have a chance to select some other module, but the checkout of the former
module is still being performed on the background.

I think Forte should offer you an option to stop the current checkout when you
click the button "<Previous" (in the step 5).
Comment 1 dmladek 2000-08-16 15:43:59 UTC
And IMHO it also should delete from the disk what it has checked out on a
background proces, I think.
Comment 2 Antonin Nebuzelsky 2000-08-16 15:55:59 UTC
Yes, but it definitely shoud not delete it automatically. I think it should
offer you this option in the dialog box as well.
Comment 3 Martin Entlicher 2000-11-29 23:05:59 UTC
It is generally not possible to find out what was checked out (the module
structure can be very complex). The kill of the checkou process may leave your
working dir in an unconsistent state. Due to these reasons I think, that it is
better to leave the checkout process continue on the background, than harm
user's working directory.
If you have any doubts, reopen the bug with some further description.
Comment 4 Antonin Nebuzelsky 2000-11-30 09:14:59 UTC
Well, a problem may arise for the user. When the user selects a module for
checkout, clicks Next and then realizes that he wanted to checkout a different
revision of this module (with "-r blabla" option), he has no other option than
checking it out again into some other directory. But what if he needs having it
checked out in the previously selected directory? He has to wait until the
checkouting finishes (but it will not be even announced!), then manually delete
the checked out stuff and start another try.

I think, Forte could stop the checkouting thread even though the directory may
be inconsistent and then ask the user if he wanted to delete the whole contents
of the working directory or leave it as it is.

If you still believe that this is not good for the user, close the bug again and
we will leave it as it is... :-)
Comment 5 dmladek 2001-01-03 18:39:59 UTC
I agree with Tonda.
IDE should ask user if he wants to stop checkouting process
and ask him if he wants to delete checked out files...
(cvs client must write it--what it checked out on stout or to some log
file) then you will be able to parse it and know what was checked out...

But there could be other droubacks...It could merge older verion with
the current one and other...

So, It isn't easy say how to solve this problem.
Becouse'of me and Martin decided to ask for help UI team...
thankx
Comment 6 dmladek 2001-02-05 12:55:59 UTC
Automaticaly changed Version from "Other" to "Dev"
Version "Other" is nonsence
Comment 7 dmladek 2001-04-10 16:37:22 UTC
This bug became obsolit with the new CVS Mouinting Wizard
Comment 8 dmladek 2001-04-10 16:38:44 UTC
Marking it as invalid, because it isn't a bug now.
If the mentioned problem still persists, pls reopen it.
Comment 9 Quality Engineering 2003-07-02 17:17:39 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.