search

gasinger / pbscc-proxy

Automatically exported from code.google.com/p/pbscc-proxy
0 stars 0 forks source link

status of locked objects is not shown with svn locks #9

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
We are a team of 3 programmers and we have just tried to switch to the "svn 
lock" locking method (we have cheched that not any object were locked with the 
"lockby" method).

The workspace objects list still displays correctly the objects locked by the 
"local" programmer, but it does not indicate anymore the locks by others (the 
red cross).

Thus, we only know that something was locked after it has failed to lock for 
ourselves.

Regards.

Original issue reported on code.google.com by sebastie...@gmail.com on 10 Aug 2010 at 12:54

Attachments:

GoogleCodeExporter commented 8 years ago 
Yes,
This is written here:
http://code.google.com/p/pbscc-proxy/wiki/PBSCCv2

just not implemented yet

Original comment by daggett....@gmail.com on 10 Aug 2010 at 4:44

GoogleCodeExporter commented 8 years ago 
Oops, all my apologies.

The new version was given by a colleague and I did not seen that this 
feature-not-implemented-yet was described in the v2 release notes.

Sorry for the noise :P

Original comment by sebastie...@gmail.com on 10 Aug 2010 at 5:41

GoogleCodeExporter commented 8 years ago 
implemented in the version pbsccsetup_2.01.73
need to be verified.

Original comment by daggett....@gmail.com on 13 Oct 2010 at 8:26

GoogleCodeExporter commented 8 years ago 
http://code.google.com/p/pbscc-proxy/downloads/detail?name=pbsccsetup_2.01.78.zi
p

Original comment by daggett....@gmail.com on 16 Oct 2010 at 6:49

GoogleCodeExporter commented 8 years ago 
Seem ok here. 

Sometimes the locked status is not displayed while the object is already locked 
by someone, but I guess that it muste be a treeview refresh problem by PB IDE 
itself and not due to pbscc (The behavior was same with the previous lockby 
property method).

Thanks for that feature :o)

Original comment by sebastie...@gmail.com on 19 Oct 2010 at 12:47

GoogleCodeExporter commented 8 years ago 
There is a description of this behavior here:
http://dm.char.com.ua/pb/pbscc/pbscc.htm

... PbSccProxy uses local cache for 1 minute (3 min in old versions)
instead of requesting real status from svn.
Now you can customize this value through registry cache.ttl.seconds value.
Also you can foce PbSccProxy to request real statuses from svn by using Get 
Latest Version on required library or target.

Original comment by daggett....@gmail.com on 20 Oct 2010 at 6:43