libmozillainterfaces-java - XPCOM bindings for Java
xulrunner - XUL + XPCOM application runner
一下是原文，小孙并没有设置 MOZILLA_FIVE_HOME变量，仅仅是安装了两个包。再次打开eclipse3.2，呵呵，没有讨厌的warning了。window->preferences->general->web browser里，可以看到原来灰色的internal web browser已经可以选择了。
事情，就是这么简单。不知道，小孙的解决方法是否能被搜索到，呵呵：）
Browser Issues
Mylar uses the Standard Widget Toolkit Browser, which means that there must be a browser on the system that works with the SWT Browser. For Windows and MacOS, the standard works fine, but on some Linux distributions, you will need to download one. Note: as of 3 Oct 2006, default Firefox distributions for Linux will not work; errors such as "Could not create Browser page: No more handles (java.lang.UnsatisfiedLinkError: ...)" may appear.
See the SWT Browser guide for which browsers will work.
Seamonkey is reported to work well. Just install and then point MOZILLA_FIVE_HOME to /usr/lib/seamonkey. (read below for example of setting this variable)
To test to see if your browser is properly configured, select Window -> Show View -> Other -> General -> Internal Web Browser, then try to bring up a web page.
-
A quick work-around is to disable the internal browser pages in Mylar editors. To do this: Window -> Preferences -> Mylar -> Tasks -> Disable Internal Browser.
-
Before testing the browser support in Mylar, you must first ensure that the Eclipse internal browser is correctly configured. To test to see if your browser is properly configured, select Window -> Show View -> Other -> General -> Internal Web Browser, then try to bring up a web page.
-
Notice: You must use the GTK2 version of Mozilla for internal browser integration.
-
Notice: The internal browser does not correctly support HTTPS. See bug 80033.
Mylar Task Management features makes use of Eclipse's internal browser, which may require additional install steps listed below. You also have the option of disabling Mylar's use of the internal browser via Preferences -> Mylar -> Tasks.
The following steps have been verified on Fedora Core 5, and OpenSuSE 10.1.
-
Run Mozilla (not Firefox) to confirm that it works.
-
Confirm the location of your Mozilla install (ex:
/usr/lib/mozilla-1.7.12) -
Set necessary environment variables in
<home_directory>/.bashrc, adding the following 3 lines
MOZILLA_FIVE_HOME=/usr/lib/mozilla-1.7.12
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$MOZILLA_FIVE_HOME
export MOZILLA_FIVE_HOME LD_LIBRARY_PATH
For Debian Etch and newer use the following MOZILLA_FIVE_HOME:
MOZILLA_FIVE_HOME=/usr/lib/iceape
- 4. Log out and log in again (or type "
source .bashrc" at the prompt) - 5. Start Eclipse and test the internal web browser
If you are getting exceptions indicating missing libraries, check that the paths are accurate and that you have the libraries required. For example, on our test box a library was still missing after these steps. The libstdc++.so.5 was being reported as missing. To solve this problem, find an rpm online that will install the missing legacy library. In our case we found necessary rpm (compat-libstdc++-33-3.2.3-47.fc4.i386.rpm) on rpmfind.net using their search facility. See also: Standard Widget Toolkit FAQ
[edit] Memory consumption problem with internal browser on Linux-GTK
If you are experiencing abnormal memory consumption upon launching the internal browser (or opening repository tasks), try shutting down eclipse, renaming/moving your ~/.mozilla/eclipse folder and relaunching eclipse. (see bug#172782)