Subversion upgrade causes subclipse to crash

I've spent a very... interesting... afternoon trying to figure how to get my eclipse development environment back on it's feet after I (foolishly?) upgraded my machine's subversion installation. Getting Subversion and my newly installed apache server on speaking terms was trouble enough. Yet I prevailed and was ready to roll up my sleeves and get back to developing. Then Eclipse wouldn't open... at all... hardly even a loading screen. Finally narrowing the issue down to subversion, I quickly deleted and re-installed the plugin. Wonderful! Eclipse is back. However, if I even had a passing thought about using an svn command eclipse would immediately dissapear without warning, leaving a stark void in my screen. After some furious searching I discovered a truly useful FAQ that described my issue exactly: http://subclipse.tigris.org/faq.html#win32-crash. Thanks, subclipse guys... it's not like you buried that one at the bottom of a long, long page or anything.

So anyone else out there who suddenly finds their eclipse + subclipse installation no longer working after upgrading to the new subversion for apache 2.2, there is a wonderful FAQ article that will fix your problem with a few simple system variable changes: http://subclipse.tigris.org/faq.html#win32-crash.

At this point I imagine other, more experienced developers sneering and then stating with a yawn, "Yes, it's really quite obvious. I can't imagine anyone spending an afternoon smashing their head on their desk trying to figure out an easy problem like this. Why didn't you just look in the subclipse faq to start with?" I wish I had a witty reply for those imaginary detractors in my head... However, I suspect I'm just paranoid. No seasoned software engineer would ever be sarcastic or mean, right? I hope this helps someone out, or at least provides the rest of you with a good laugh at my expense.