Eclipse, Subclipse and Subversion 1.3
Uncategorized
Bottom line, dont install subversion 1.3 (new release on 1/6/06) while using subclipse 0.9.3 (current). Doing so will cause eclipse to crash in such a terrible way that it takes down the hole JVM with it. For the full (long and rambling) story please read on.
During all of this, you never bothered to check the Subclipse web site or mailing lists? There has been a 1.3 compatible version of Subclipse since RC1. It was not on the main update site since Subversion was not GA yet but the info was on the web site in the release announcements and the changelog.
The 1.3.0 version of Subclipse was just released today but had to be pulled back due to a problem with JavaSVN. It will be out again soon.
Finally, at least with the recent versions of Subclipse (0.9.100+) once you have selected JavaSVN in your preferences, it shouldn’t matter if you have a newer version of Subversion installed since it will not ever try to load JavaHL. Of course, this version also supports/requires Subversion 1.3.0 anyway, but it could probably come up again with 1.4 or some other future release.
Good info. I use CFEclipse/Subclipse/Tortoise and always wait until all three are synced up before upgrading any one component. Thanks for the heads up on 1.3
Jim
Hey Mark,
I appreciate your comments. I did check the website and the announcements page. I missed the changelog which would have explained the jump from 9.37 to 9.100.
However after I figured out it was subclipse that was having problems in eclipse, I realized that it wasnt really subclipse fault (so I was not about to bother folks on the mail list). I installed software that was incompatible and that was the intent of this post, was to make sure others dont make the same mistake.
I am excited to see that a new release almost made its way out the door today. Since most of my problems were resolved by last night, this release would not have helped me much.
Anyway, I see that you are the project owner for the subclipse project and so i will take this time to say Thanks! I appreciate all your work on a plugin that makes my life easier on a daily basis!
I solved this in a slightly different way. I found it easier to reach in to the Eclipse plugins directory and move the org.tigris.* classes out to a holding location. Then I could restart eclipse and download the newer version of the plug-in cleanly.