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

Re: javahl.ClientException: Working copy not locked?

From: Brendan Duddridge <brendan_at_clickspace.com>
Date: 2004-08-13 07:07:52 CEST

Well, if they had included invisible (i.e. Folders that start with a period)
in the copy to the new EOModel copy, it would have worked just fine. I
originally thought maybe it was some special case where EOModeler looked for
a CVS folder, so I created a test SVN folder in my model folder and
EOModeler maintained that folder just fine in the new copy. It's probably a
very minor change to fix the bug. Just include invisible folders when doing
the backup and everything is A.Ok.

Isn't there a way to extend EOModeler with bundles that might be able to fix
this? I remember there being an EOModeler bundle a long time ago that fixed
the CVS issue. Maybe it could be modified to fix the .svn issue too. Any
Cocoa developers out there willing to take on the challenge? Please?


Brendan Duddridge

ClickSpace Interactive Inc.
Suite L100
239 - 10th Ave SE
Calgary, AB T2G 0V9
(403) 277-5591

> From: Ashley Aitken <mrhatken@mac.com>
> Date: Fri, 13 Aug 2004 12:58:23 +0800
> To: "Brian W. Fitzpatrick" <fitz@red-bean.com>
> Cc: <users@subversion.tigris.org>, Brendan Duddridge <brendan@clickspace.com>
> Subject: Re: javahl.ClientException: Working copy not locked?
> On 13/08/2004, at 10:45 AM, Brian W. Fitzpatrick wrote:
>> Wait, don't! There's a way to get around this--just check out a copy
>> of your EOModel somewhere else, and copy the .svn directory into the
>> eomodel with your changes in it. That way you don't have to redo your
>> changes.
> Yes, I thought of that after I had posted (it was late ...).
>>>> Oh, and watch out in the future--I don't think EOModeler is .svn
>>>> savvy.
>>> So why doesn't EOModeler just make a copy of the EOModel into the
>>> backup copy rather than, as it would seem, moving the old model and
>>> creating a new one!? (Rhetorical question)
>> Because EOModeler is an old, sucky, crufty piece of software that
>> should be taken out back and shot (Rhetorical answer).
>> :-)
> Sad but very true.
>>> This seems very problematic for use with SVN?
>>> Is there any workaround ... I'm not sure how to "watch out" in this
>>> situation?
>> See above.
> Ouch, that's not very nice at all. I guess that is what developers who
> used CVS had to do as well (apart from using cvswrappers or similar).
> Cheers,
> Ashley.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 13 16:23:39 2004

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

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