Getting "CHECKOUT can only be performed on a version resource" when trying to commit using Eclipse subversive plugin
Solution 1
Cleaning up worked for me:
right click on the project -> team -> cleanup / refresh
Solution 2
As I commented in other post...
For those that project -> team -> cleanup doesn't work in eclipse try:
- Force the cleanup using SVN Tortoise
- From terminal with command
svn cleanup /folder_to_cleanup
Solution 3
This is most likely your console svn version is different to your Eclipse "SVNKIT (Pure Java)" version, you can change Preferences=>Team=>SVN=>SVN interface=>Client using "JavaHL (JNI)"
My case is as below, using Java HL 1.7.10 is ok, but using SVNKIt v1.7.9 will have the problem
wuliang-Mac:src wwu$ svn --version
svn, version 1.7.10 (r1485443)
compiled Jul 9 2013, 12:55:03
Solution 4
There is bug reported in SVNKit with the same error.
Solution 5
Try to execute from the terminal:
svn cleanup
Team -> Refresh/Cleaunp from IDE didn't work for me.
Dave
Updated on September 11, 2020Comments
-
Dave over 3 years
I'm using Eclipse Juno on Mac 10.7.5, SVN 1.7 and the Eclipse Subversive plugin. Occassioanlly, when I try and commit changes from my project (by right clicking on the project from the package explorer, selecting "Team" -> "Commit"), I get the error:
Some of selected resources were not committed. Some of selected resources were not committed. svn: E200007: Commit failed (details follow): svn: E200007: Commit failed (details follow): svn: E200007: CHECKOUT can only be performed on a version resource [at this time]. svn: E175002: CHECKOUT request failed on '/svn/subco-digital.coderepo/!svn/rvr/2110/trunk/myproject/src/main/java/org/mainco/subco/myproject/validator/UserFormValidator.java'
I have verified that I have checked out the latest version of my project. How can I take care of these repeated errors?
-
Dave over 10 yearsThanks for this feedback. I'm having trouble getting Eclipse to recognize the JavaHL SVN connector - am currently using the SVNKit connector. Going to troubleshoot that issue and if that turns out to be the problem, I'll come back and accept.
-
David over 9 yearsFWIW, this seems to be related to checking out an SVN repository with one version of the SVN client then trying to manage it in Eclipse using a newer version.
-
NathanChristie almost 9 yearsHere is a google cache of the issue for anyone scared to click: webcache.googleusercontent.com/…
-
tak3shi almost 8 yearsNothing new, check @wuLiang´s answer. You have used different versions of SVN clients.
-
JuanN over 7 yearsSometimes I had to force the cleanup using SVN Tortoise, since Eclipse cleanup didn't work.
-
FLBKernel over 6 yearsAnyway, @khituras I recommend you to change from svn to git :P
-
khituras over 6 yearsOh, I already did, but there are still old projects in svn :-D
-
mike over 6 yearsThanks @David. I did the checkout with Tortoise, but tried to commit in Eclipse.
-
Kumar S over 6 yearscleanup from Eclipse is not working for me. Cleanup from SVN Tortoise worked great!
-
FLBKernel over 6 yearsThis answer would be ok if the question was for Intellij. However it is for Eclipse subversive plugin.
-
LeOn - Han Li over 6 years@FLBKernel, i was led to this question when google searching this SVN error. So i thought it might save some other
Intellij
user some time in case google also take them here. Anyway~~ -
fchen about 6 yearsI had to do 'svn cleanup' from the command line. After that in Eclipse I do refresh, then team->refresh/cleanup
-
fchen about 6 yearsbtw, in my case I think it's related to the fact that I used chmod to remove the executible bit of some files and changed the content as well. I later figured out that I have to use 'svn propdel' to do that.
-
Soumyajit Swain over 5 yearsIn my SVN Connector only one option is available for select.That is SVNKit 1.8.12..Do I have to download the additional connector.
-
Aravindh Gopi over 5 yearsyes, you can download them here
-
Soumyajit Swain over 5 yearsIt worked for me and I managed to checkin from eclipse instead of falling back on tortoise client
-
megadave over 5 yearsHad the same problem with Netbeans. Changing the Client from SvnKit to CLI solved the problem for me.
-
Christopher Schultz about 5 years
svn cleanup
worked for me in a way that none of the other suggested interventions on this page did. Thanks! -
Sean N. about 4 yearsOn MacOS I used "brew reinstall svn" followed by "svn cleanup /folder_to_cleanup". Worked great.
-
Cody almost 4 yearsI thought this question was useful despite not being eclipse related. Good for people who are directed here by the same google search.
-
Sudeepa Nadeeshan over 2 yearsThis is the common case for 2020-06 (4.16.0). You have to use the terminal to do the cleanup.