All locking problems, including this one are resolved in 1.2.0 release.
That being said, unless your server is not running Subversion 1.2+ the LOCK
method ought to work regardless. So you might want to look into that. You
might have a proxy that is blocking that method. That being said, with
1.2.0 you would just be prompted to remove the read-only flag and it would
do it for you.
Mark
On 5/4/07, Hugo de Oude <HdOude@allshare.nl> wrote:
>
>
> Hello,
>
> The following situation results in a RA layer request failed:
>
> - We do have a certain class in package a.b.c which is controlled
> with SVN and not locked at the moment.
> - When we do a refactor in MyEclipse by selecting this class and
> moving this to an other package,
> a popup box is shown.
>
>
> We answer YES to this question. Keep in mind I did not Lock the
> particular Class before this refactor.
> - Then the Class is moved to the new package.
> - However when you start editing the new class, it automatically
> asks us to lock the Class. When you lock this class the following
> error is shown:
> RA layer request failed
> svn: Lock request failed: 405 Method Not Allowed
> - This can be solved by unchecking the Read Only flag on the Class
> within the Properties window.
>
>
> There is a work around for the problem above. You can assure the above
> will work correctly if you acquire a Lock on the class *before* you do the
> actual Refactor.
> Then there won't be a problem.
>
> *Can somebody fix the abovementioned problem when we decide not to acquire
> a Lock?*
> Thanks in advance.
>
> *Other information:*
> IDE = MyEclipse Version: 5.1.0 GA Build id: 20061111-5.1.0-GA
> Operating system = Windows XP
> The release and/or revision of Eclipse = Eclipse 3.2.1
> The release and/or revision of Subclipse = 1.1.9 (because 1.1.10 and
> 1.2.0 do have a locking problem as reported in a previous email to
> users@subclipse.tigris.org)
> The client adapter used (JavaHL or JavaSVN) = JavaHL
> The protocol used (file://, svn://, http:// etc.) = http://
>
> Cheers,
> Hugo
>
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on Fri May 4 13:59:39 2007