tag:blogger.com,1999:blog-17823979.post6054645587990563832..comments2023-09-29T05:03:51.672-04:00Comments on DivByZero.com: My love-hate with SVN, Part 3: CollabNet Subversion (JavaHL)nickbhttp://www.blogger.com/profile/09200865148587349560noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-17823979.post-48184052858008509262011-04-15T07:52:40.399-04:002011-04-15T07:52:40.399-04:00It's most likely to do with case sensitivity o...It's most likely to do with case sensitivity on the repo URL. It's case INSENSITIVE when checking out but case SENSITIVE when committing. <br /><br />I scratched my head for a couple of hours with exactly the same problem, that checkout is not a problem but a 403 forbidden comes when trying to commit.<br /><br />I.e. if the correct repo URL is http://acme.com/svn/Acme but you checked it out as http://acme.com/svn/acme it won't work.Unknownhttps://www.blogger.com/profile/12655943466147337323noreply@blogger.comtag:blogger.com,1999:blog-17823979.post-64365270254125532022008-12-19T06:44:00.000-05:002008-12-19T06:44:00.000-05:00rm -Rf ~/.subversion/auth is my new phrase of the ...rm -Rf ~/.subversion/auth is my new phrase of the day, cheers mate :DUnknownhttps://www.blogger.com/profile/10630251031273913400noreply@blogger.comtag:blogger.com,1999:blog-17823979.post-61418616776386868652008-12-05T14:17:00.000-05:002008-12-05T14:17:00.000-05:00Wasn't doing anything w/ Maven, but your suggestio...Wasn't doing anything w/ Maven, but your suggestion to blow away the cached credentials *did* work. Thanks!<BR/><BR/>(I wonder if any of this week's rant should be digested into a FAQ on your site? I can't be the only person with these issues.)nickbhttps://www.blogger.com/profile/09200865148587349560noreply@blogger.comtag:blogger.com,1999:blog-17823979.post-18934627300001149492008-12-05T11:49:00.000-05:002008-12-05T11:49:00.000-05:00A 403 would imply your credentials were not valid....A 403 would imply your credentials were not valid. JavaHL and SVNKit do each have their own distinct cache so perhaps the one for JavaHL has something unexpected from a previous usage? JavaHL shares the same cache as the command line so in theory a commit using the command line client should have the same problem.<BR/><BR/>You can rm -Rf ~/.subversion/auth to clear your cached credentials. You should then be prompted again in Eclipse the next time you need to provide them.<BR/><BR/>Searching for "svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request" does give some hits though. Were you doing something with Maven when you did this? I see a lot of people with Maven problems. Looks like it is a bug in SVN since 1.5.1 release.Mark Phippardhttps://www.blogger.com/profile/16905022252385982106noreply@blogger.comtag:blogger.com,1999:blog-17823979.post-11005808123100011312008-12-05T11:42:00.000-05:002008-12-05T11:42:00.000-05:00Well, tried the JavaHL layer for the first time to...Well, tried the JavaHL layer for the first time today and got this trying to commit a change to a file:<BR/><BR/><I>RA layer request failed<BR/>svn: Commit failed (details follow):<BR/>svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request for '/repos/devstudio/!svn/act/4f5425fd-c29d-4f84-8c85-826cdfb06571'</I><BR/><BR/>So, I've gone back to SVNKit, which does work. Will the madness never end?nickbhttps://www.blogger.com/profile/09200865148587349560noreply@blogger.comtag:blogger.com,1999:blog-17823979.post-71229931975474096592008-12-05T08:46:00.000-05:002008-12-05T08:46:00.000-05:00I will try to update the Wiki based on your commen...I will try to update the Wiki based on your comments. The Wiki is an attempt to explain the JavaHL issue to users so that they can understand how to get it working and also why it cannot simply be distributed with the plugins.<BR/><BR/>To answer some questions:<BR/><BR/>The JavaHL path you need is the one to the native library. The JAR comes with Subclipse/Subversive you need to supply the library (libsvnjavahl-1.so). This is usually in /usr/lib/jni or /usr/lib or /usr/local/lib. One of the problems in dealing with Linux is that the location varies.<BR/><BR/>I think the reason you were not able to use SVNKit is that you had a copy of its JAR in that global Java extensions folder. I am surprised Subversive did not have the same problem. I will contact the SVNKit authors to see if there is something we could have done.<BR/><BR/>I did not link to the CollabNet Subversion binaries because I maintain those binaries and did not want to seem like I was just promoting them as the only option. You can use the JavaHL from your distro, I think you just were not entering the right path.Mark Phippardhttps://www.blogger.com/profile/16905022252385982106noreply@blogger.com