[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] Another bug in new locking code in 1.1.9

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-01-05 12:20:25 CET

On 1/5/07, Thomas M. Hofmann <email@thomashofmann.com> wrote:
> sorry for replying so late. I loaded your changes and now the file is left
> read-only when it is locked by another user.
> Unfortunatley, I noticed another problem while trying to lock a file that is
> not locked at all. The SVN decorator turn to the black and white checkmark
> but the file stays read only (I refreshed the resource manually and checked
> on the file system). I know that svnkit will chnage the read-only attribute
> and I tried to debug into the code that does so but I hadproblems because it
> it not so easy to find the source code for svnkit that matches the line
> numbers used in the svnkit jar bundled with subclipse. Since I did not have
> much time the past days I did not succeed to find the cause for this
> problem.
> I hope that I have some time this evening and I will 1) check if this also
> is a problem with javahl and 2) try to get svnkit debugged.
> I thought I'd report this now since you might already know what is causing
> this. If you don't I'll post more info hopefully this evening (CET).

The current code is back to how it used to be in this regard. Namely,
we now expect and assume that the client interface (JavaHL or SVNKit)
will behave properly and make the file writable when the
svn:needs-lock property is present and the file is successfully
locked. I'd be surprised if JavaHL had a problem here. We could
report the problem to SVNKit. I'd assume it would be consistent but
it sounds like it is not.

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Fri Jan 5 12:20:31 2007

This is an archived mail posted to the Subclipse Dev mailing list.