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

Re: [Subclipse-users] lock errors

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-08-22 02:15:26 CEST

"Cain, Tom" <tcain@solekai.com> wrote on 08/21/2006 03:46:40 PM:

> As mentioned in a previous post, we intend to use the ISVNClientAdapter
> within a plugin we are developing. However, one thing I noticed is that
> errors are not thrown as exceptions, but rather posted to the
> ISVNNotifyListener. For example, the ISVNClientAdapter.lock method does
> throw an exception in either of the following two error cases:
> 1. Another user has the file locked
> 2. The local file is not up to date with the SVN repository
> Instead, the ISVNNotifyListener.logError is invoked with the error
> I understand different error handling strategies exist, but I would
> that there would be some indication to the caller of the lock method
> the lock failed (i.e. a Boolean return value, an exception, etc). Is
> the expected behavior? Is there any plans on improving the API to return

> error information?

It looks intentional. The commit message for r1795 is:

Updated Lock/Unlock methods. Removed some workarounds for 1.2 issues that
are resolved in 1.3.

Do not throw exceptions when options fail. Just log to console.

Your notification handler should be able to know the command being
executed, and it calls the logException method of the handler. You
couldn't deduce the error from that if you need to know the specifics?


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Aug 22 02:15:49 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.