Since joining JBoss, a division of Red Hat, I've gotten to know the foibles of SVN rather intimately. Here are my two favourites, both encountered this week:
This client is too old to work with working copy; please get a newer Subversion client.Problems reported while synchronizing SVNStatusSubscriber. 2 of 3 resources were synchronized. An error occurred synchronizing /devstudio-workspace: Error getting status for resource P/devstudio-workspace org.tigris.subversion.javahl.ClientException: svn: This client is too old to work with working copy; please get a newer Subversion client
This happens if you use SVN 1.5.4 and Subclipse 1.4.6 with SVNKit & JavaHL plugins. Solution? Switch to Subversive 0.7.5, or follow this advice (so I'm told, I haven't tried yet).
- Installing subversion-javahl-1.5.4-3.i386 (on Fedora 10 Rawhide) causes Ant 1.7.1 to fail to do SVN checkouts.
(from /var/log/yum.log) Nov 27 19:51:47 Installed: subversion-javahl-1.5.4-3.i386
[java] fetchElement: [java] # [java] # An unexpected error has been detected by Java Runtime Environment: [java] # [java] # SIGSEGV (0xb) at pc=0x05984ec5, pid=24986, tid=3086982032 [java] # [java] # Java VM: Java HotSpot(TM) Server VM (11.0-b15 mixed mode linux-x86) [java] # Problematic frame: [java] # C [libapr-1.so.0+0x1fec5] apr_threadkey_private_get+0x15 [java] # [java] # An error report file with more information is saved as: [java] # /opt/public/jbt-jbds/nightly-20081128-0002/org.jboss.ide.eclipse. releng/builders/hs_err_pid24986.log [java] # [java] # If you would like to submit a bug report, please visit: [java] # http://java.sun.com/webapps/bugreport/crash.jsp [java] # The crash happened outside the Java Virtual Machine in native code. [java] # See problematic frame for where to report the bug. [java] # [java] Java Result: 134(from /var/log/yum.log) Dec 02 11:19:23 Erased: subversion-javahl
And now it works again!
3 comments:
I've settled in on a hate-hate relationship with SVN. No use being in denial.
This is why SVN should be elevated to first class team provider in Eclipse on par with CVS and not left as a plugin.
It would make things a lot less painful (and save me the hassle of installing SVN plugins for every developer).
Seems to work fine for Netbeans.
I agree. I'm fighting with Subclipse on OSX and losing, it completely crashes Eclipse every time (as in it vanishes...). It could be that I'm using svn+ssh, but this is a supposedly supported protocol, and it certainly shouldn't bomb, so I'm forced to use a separate client. SVN seems to be the defacto standard at the moment if the job boards are anything to judge by, and all the non-MS shops I've worked for use SVN and not CVS. I'm hating subclipse to the point that I might use a separate application to manage versions.
Post a Comment