news <news@sea.gmane.org> wrote on 01/16/2006 08:52:22 AM:
> updating Subversion client to 1.3 but keeping Subclipse 0.37 in Eclipse
3.1
> causes consistent and systematic crashing of Eclipse at startup
> (on Mac OS X 10.4.4, JDK 1.5.0_05).
>
> Workaround is to remove subversion plugins manually and re-install
> Subclipse 0.104.
>
> This is quite annoying and it should not be forced upon a user who
> does not wish to upgrade Subclipse just yet.
>
> Or - at least - it should be made clear in the Release notes that
> one should first upgrade Subclipse (or change to JavaSVN)
> and then upgrade Subversion to 1.3.
>
> Alternatively, another release that does not mandate but supports
Subversion 1.3
> JNI?
>
> Minor points - granted.
> Thanks for great work, otherwise.
How could the release notes for 0.9.37 tell you that a future version of
Subversion that did not exist at that time was going to cause it to crash?
Why would you happily upgrade Subversion binaries to a new release, but be
concerned about updating Subclipse to the equivalent new release that goes
with those binaries? Especially when that Subclipse release is a 1.0
Release Candidate and represents a vast improvement over that version?
Finally, it is JavaHL that is crashing, not Subclipse. Your request
should be to the Subversion developers about whether they want to consider
allowing older versions of their svnjavahl.jar work with newer versions of
the libraries. I suspect that they consider them a matched set.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Jan 16 20:36:24 2006