dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

File Modification Indicator problems

( CVSSCC )
Type: Public Status:Closed Created: 12 Jul 04 07:00 Updated: 12 Jul 04 07:00
--> Igor Pushkov (admin)  at 12 Jul 04 07:00 writes

You are right, other GUI client looks at file timestamp to determine
if file "edited" or in terms of IDE "checked out". However this can
cause some confusion. You may know, that there two ways with CVS to
provide edit cycle for file:
1. Remove read-only flag/or and/just edit it -- commit changes
2. cvs edit -- edit file -- commit changes
With first behavior there are two bad things:
a) you not inform others that you edit file. This way unexpected
conflicts can occurs.
b) this is some paradox, but you can find that in such case "cvs
unedit" command does not revert file back.
For us it is import to get away from such things. User will be very
surprised when on "Undo checkout" nothing will happens. And so on.
That's why, by default we follow ideology of "strict checkout
status". I.e. we consider file as checked out (modified) when "cvs
edit" or "Checkout in IDE" applied to it. As the result the cvs/base
folder will contain pre-checked out copy of file, all others are
notified, virtual reserved checkout mode working, undo checkout is
guaranteed.
However, you can switch off this option in configuration, and
plug-in will follow the other GUI's logic. I.e. file will be "checked
out" when file date/time is modified or "cvs edit" is applied. Only
one thing, is that to display correct status you should explicitly
call "refresh status" command from IDE.
The "Check Server for File Status" achieve the same result, but you are
right, it is slow. The purpose of this option is bring up additional
statuses like "need update" or "check out by some one else". But we
know only one IDE that display such statuses, it is PowerBuilder. If
you use other IDE you not need to use this option.
I hope this will answer your question.
--> Jeanne Webb (user)  at 12 Jul 04 07:00 writes

We're having problems with the way the CVSSCC Proxy handles its detection
of file modification. We use several CVS clients against our source code
on developer's workstations. When we do this, it seems to interfere with
the way CVSSCC handles the detection of modified files. We enabled the
"Check Server for File Status" check box in the configuration screen, and
this seems to make it see the modifications correctly. However, with this
option set the time it takes to open a project is unbearable. Can you tell
me how the client is checking for modifications on files when it is not
going against the CVS server? Would it be possible for you to look at the
timestamp on the file? This is the way most CVS clients determine local
modification but it seems your client is doing it in some other way.

Thanks,
Andrew Schaefer
andrew.schaefer@bentley.com
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9752306 visitor since 20 Jan 2003.
3260 visitors today and 14 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com