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

[Subclipse-users] Problem with Read-only attribute after moving a SVN controlled class

From: Hugo de Oude <HdOude_at_allshare.nl>
Date: 2007-05-04 11:56:54 CEST


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
Received on Sat May 5 10:23:44 2007

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.