On Dec 27, 2007 6:16 PM, Mansour <email@example.com> wrote:
> Mark Phippard wrote:
> > On Dec 27, 2007 10:55 AM, Mansour <firstname.lastname@example.org> wrote:
> >> I am using linux and that's what cam when I installed subclipse from the
> >> update site. When I checked the preferences javahl was the default
> >> package but there was an error message as it was not available. However,
> >> I switch it to SVNKIT and the error message went away but still I can
> >> not create a project and I am getting the same error !!
> > There is no reason SVNKit should not work, but since it
> > reverse-engineers the protocols, it is possible there is a subtle
> > difference that is triggering a problem in your setup. Using JavaHL
> > would cause the native libraries to use. Most Linux distributions
> > offer a package for JavaHL now. So that might be an option to pursue.
> > The problem is that there is nothing else we can do. We just execute
> > a high-level checkout API. All the real works happen in the libraries
> > (JavaHL or SVNKit) and is beyond our control.
> I think you can something great. Just include javahl with the default
> installation for linux.
CollabNet is going to start including it for RedHat and RPM-based
distributions when 1.5 ships. It is harder than it sounds though.
Subversion uses a lot of other libraries so you cannot just make a
single version that works anywhere.
> I can not find it there and I am looking into
> install it manually. On the other hand I don't think the prefrences for
> selecting SVNKit or javahl is working properly becuase even when I
> choose SVNKit I still get an error about javahl client initialization !
> Do you know do I install javahl on linux ??
It varies by distribution. Debian/Ubuntu just have packages in apt
you can install. Other distributions also have it available.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Dec 28 01:02:40 2007