On 1/3/07, Keith Irwin <keith.irwin@gmail.com> wrote:
>
>
> On 1/3/07, Mark Phippard <markphip@gmail.com> wrote:
> >
> > On 1/3/07, Keith Irwin <keith.irwin@gmail.com> wrote:
> > >
> > >
> > >
> > > When I click on the SVN preferences tab, eclipse tanks. Yes, I used
> > > the same jvm to compile javahl as is running eclipse.
> > >
> >
> > JVM should not factor into this. JavaHL is a C++ library that uses the
> > SVN C libraries. We provide the JavaHL Java part with Subclipse. You do
> > not need to touch that, nor should you. You do need to build the native
> > library and make it available.
> >
>
> You mean the jar file? I just added the -vmargs -
> Djava.library.path=/usr/local/lib thing (in which is the .so under
> discussion).
>
> BTW, another developer also has the same symptoms. Once he changed his NT
> domain password, he can no longer use eclipse to update or commit. He has
> to use the commang line. He can, however, use Windows. I can use the Mac
> (though don't have access to it at the moment).
>
> It seems that the problem is on linux. Far as I can tell, the Windows
> installation is using javahl.
>
> I'm going to try a new installation of everything on a machine that has
> never had eclipse installed and see what happens.
>
> I still can't get eclipse to not fail when I add the above path to the
> command line.
>
New info:
I installed eclipse, callipso and subclipse 1.1.9 on a "new" ubuntu linux
box. Same problems as before. I also installed the libsvn-javahl package,
which places libsvnjavahl-1.so in /usr/lib/jni.
I started eclipse with:
./eclipse -vmargs -Djava.library.path=/usr/lib/jni
and when I surfed to the Window -> Preferences -> Team -> SVN page, eclipse
tanked.
Apparently, Ubuntu + Eclipse + javahl is a no go.
Regardless, none of this explains why everything worked just fine BEFORE I
(and my colleague) changed our NT passwords as per IT policy.
Strange, eh?
Keith
Keith
>
> I guess this is all a bust. I suspect it has nothing whatsoever to do
> > > with subclipse. 1.0.4 doesn't work either.
> > >
> >
> > That would be expected as it uses the exact same code to access SVN as
> > 1.1.9.
> >
> > Works fine on the mac, though. Very strange. ;)
> > >
> >
> > Is the Mac using JavaHL or SVNKit in the preferences? If the latter,
> > then it should work on Linux as well. If it is using JavaHL then that is
> > the difference.
> >
> > Thanks
> >
> > Mark Phippard
> > http://markphip.blogspot.com/
> >
>
>
Received on Wed Jan 3 23:51:40 2007