Subclipse is 1.6.2, RPM is CollabNetSubversion-client-1.6.0-5.i386.rpm
-David
> What versions of Subclipse and the RPM are you working with?
>
>
> On Wed, Apr 1, 2009 at 4:31 AM, David Resnick <abunetta_at_gmail.com> wrote:
> > I'm having the same problem. I have the latest Collabnet Subversion client RPM installed as well.
> >
> > Is it possible that there is a problem with the path which is preventing the JavaHL from finding the Subversion libraries?
> >
> > Thanks,
> > David
> >
> >
> >> On Mon, Mar 30, 2009 at 6:43 AM, Mika Laitio <lamikr_at_pilppa.org> wrote:
> >> >>> We all have this tendency to want the 'latest and greatest'(me too). I
> >> >>> kept getting the same error on an up-to-date Ubuntu 8.10 linux(Intrepid
> >> >>> Ibex) but I kept trying to use the 1.6 version. When I got the software
> >> >>> and components from the http://subclipse.tigris.org/update_1.4.x site it
> >> >>> started working.
> >> >>>
> >> >>
> >> >> I had the exact same issue on a newly installed 3.4.2 on a 32-bit Vista
> >> >> machine. 0.7 and 1.6 would not recognize any adapters I loaded. Once I
> >> >> went back to http://subclipse.tigris.org/update_1.4.x , everything was
> >> >> happy. Thank you for posting this - I was going crazy trying to get it to
> >> >> run at all...
> >> >
> >> > This is only partially true at least in my case.
> >> > Because I updated my Mandriva to newer version, I got 1.6.0
> >> > version of subversion and libsvnjavahl-1 library.
> >> >
> >> > Once I got my original (mandriva bug in the libsvnjavahl-1 library
> >> > install) fixed, also the subclipse 1.6.0 started working ok.
> >> >
> >> > But if I used another eclipse 3.4 instance which had plugins from the
> >> > subclipse-1.4.x branch, then the commands like "show history" in the java
> >> > or c++ perspectives crashed.
> >> >
> >> > So it seems that libsvnjavahl libraries are not backward compatible.
> >> > (and they start use numbering instead of claiming that the library version
> >> > is always 0.0.0, like libsvnjavahl-1.so.0.0.0)
> >>
> >> The library is backwards compatible, but only if you use a matched JAR
> >> and library. Subclipse 1.4.x includes JavaHL 1.4 Java code. So this
> >> refers to native methods that no longer exist etc. So you really need
> >> use Subclipse 1.6.x.
> >>
> >> I intended to have our code that loads the JavaHL library reject the
> >> library if it is the wrong version. I just forgot to update it when
> >> 1.6 comes out. I committed the fix for the 1.6 version last week, and
> >> will doing a fix for 1.4.x this week. The intent is for 1.4.x to
> >> report JavaHL as "Not available" if the version of the library is
> >> wrong.
> >>
> >> --
> >> Thanks
> >>
> >> Mark Phippard
> >> http://markphip.blogspot.com/
> >
> > ------------------------------------------------------
> > http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=1504753
> >
> > To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
> >
>
>
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=1507043
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-04-01 15:33:56 CEST