Did you fiddle with the eclipse.ini or command line start options? Go
into Help > About and then Configuration Details to see if you can
still see those customizations.
If Eclipse is starting with command line options it ignores anything
in eclipse.ini.
Mark
On Mon, Mar 16, 2009 at 4:38 PM, <webpost_at_tigris.org> wrote:
> I'm currently running CentOS 5.2, x64, along with Eclipse 3.4 and Subclipse 1.4. I'm also using Sun's JDK 1.6.12.
>
> I just installed a clean Eclipse Classic (3.4) and the latest Subclipse 1.4 from the update site.
>
> Since CentOS 5.2 does not include Subversion 1.5+, nor does it include JavaHL bindings, I had to compile Subversion from source.
>
> I built a custom RPM, and the JavaHL bindings were installed successfully.
>
> The only time Eclipse correctly displays the SVN interface as "JavaHL (JNI) 1.5.6.." is when I use a brand new workspace, that hasn't been created yet. As soon as I close Eclipse and re-open the newly created workspace, Eclipse goes back to reporting "JavaHL (JNI) Not Available"
>
> Any hints on how to get this to work permanently?
>
> I've been using SVNKit as the sole workaround to this issue.
>
> ------------------------------------------------------
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=1335270
>
> 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=1335301
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-03-16 21:44:55 CET