[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-dev] tip for running subclipse on ubuntu to resolve the javaHL library issue

From: Bryan Ward <wardbt_at_hotmail.com>
Date: Wed, 2 Feb 2011 12:46:12 +0000

Hello,

I've recently managed to get subclipse running in eclipse running on ubuntu
linux. like most people I had the same issues with the javaHL library.

What I found is that in order to work properly you have to add the
-Djava.library.path parameter to the eclipse.ini file at the end.

e.g. this works

cat /etc/eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.200.v20090520
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vm
/apps/java/jdk1.6.0_23/bin/java
-vmargs
-Xms512m
-Xmx768m
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins
*-Djava.library.path=/usr/lib/jni*

whereas this *didn't*

cat /etc/eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.200.v20090520
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vm
/apps/java/jdk1.6.0_23/bin/java
-vmargs
*-Djava.library.path=/usr/lib/jni*
-Xms512m
-Xmx768m
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins

I could tell it was reading my eclipse.ini file because I could see the
heapsize change take affect but then was confused why the library path
wasn't showing up in the configuration.

I'm just sending you this because I think this documentation might want to
be updated with this tip.

http://subclipse.tigris.org/wiki/JavaHL#head-edfd418b80cac560a2557a9251b0e6ae5e95f0ad

You can tell if JavaHL has loaded by looking at the Eclipse preferences
under Team > SVN. If the library loaded correctly you will see the version
of the library, otherwise it will show "Not available". If a version of the
library that is too old to use is found, then we do not load the library and
it will show as "Not available".

A common problem that Linux users have run into is that they edit the
eclipse.ini file to point to the path where the library is loaded but it
still does not work. Something to check if this happens to you is whether
the settings in the INI file are being used. A lot of users customize the
launcher they create to run Eclipse and they include some command line
options for starting Eclipse. When you do this, it appears that the Eclipse
launcher does not use any of the settings in the INI file. The easiest way
to see this is happening is to do Help > About in Eclipse and then choose
Configuration Settings. If you look through the settings you should
eventually be able to see the command line settings used for the JVM. If you
do not see the java.library.path line then it was not used.

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1043&dsMessageId=2701940

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2011-02-02 13:47:45 CET

This is an archived mail posted to the Subclipse Dev mailing list.