"B. Smith-Mannschott" <firstname.lastname@example.org> wrote on 05/18/2006 11:34:29 AM:
> This problem surfaced because I have written a small CGI script which
> pushes the output of ``svn info --xml`` through a transformation to
> generate an overview of currently locked files. This, in turn works
> around a defect in *subclipse*, whereby it will tell you when you
> can't lock a file because someone else has the lock, but won't tell
> you *who* has the lock.
Hopefully this will not sidetrack any discussion on your bug report, I
just wanted to comment on your last part. This is not a defect in
Subclipse, it is a design-decision by the Subversion (not Subclipse)
developers to not carry this information in the local WC. Neither
Subclipse, nor TortoiseSVN, show locks by other users in their decorators
due to this limitation. There is room for enhancement in Subclipse to
provide options that let you go check if there is an active look. I find
it odd that you have never posted anything to any Subclipse mailing list.
If users do not ask for enhancements, they tend to not be made. We have
not put too much effort into what I would call "advanced" lock features in
Subclipse, because we cannot see the typical user using this feature of
Subversion. So we decided to take a wait and see on the issue. Meaning,
wait and see if people ask for more features.
FWIW, the Subclipse SVN Repository browser has an option that will show
the current lock information for a file. I suspect you could have
submitted a patch to add this feature into Subclipse with less effort then
it took to code your workaround. There is already a Subversion properties
page that shows the output of svn info on the local path. You would just
have to extend this to run it on the URL to check for active lock
information. The dialog even already has the lock fields on the display.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun May 21 20:33:29 2006