Eclipse and Eclipse Plug-in Installations
|COMP 310 Java Resources Eclipse Resources|
Please see the Comp310 Java Resources page.
If you already have Eclipse installed, follow the directions on the Eclipse home page to upgrade to the latest version. There are also instructions there on how to set Eclipse to always upgrade to the latest version.
If you are running a 32-bit operating system, please contact the staff immediately BEFORE installing anything! (Recommendation: upgrade to a 64-bit operation system as a 32-bit system will only cause one problem after another.)
Note: Particularly if you have upgraded Eclipse from an earlier version, e.g. Kepler to Luna, you may need to increase the amount of memory allocated to Eclipse in order to gid rid of "Out of Memory" or "GC Overhead Limit Exceeded" errors. If you are encounter these errors, please see these directions.
Keep Eclipse Updated! -- Periodically, run Help/Check For Updates from the Eclipse main menu.
Eclipse itself is a Java program and is thus run by a specific JVM. The JVM that runs the Eclipse app is NOT necessarily the same as the JVM to which it is compiling and running developer code! Having a difference in the JVM running Eclipse vs. the JVM to which Eclipse is compiling and running developer code, especially if the former is an older version, the can lead to strange, seemingly unrelated problems both during compilation and running of developer code as well as in the operation of some Eclipse plugins. WindowBuilder, for instance, is well-known for being very sensitive to a discrepancy in JVM versions.
The discrepancy in JVM versions between the one running Eclipse itself vs. the one to which it is compiling and running developer code is often caused by having an older JVM version installed when Eclipse was installed. When Eclipse installs, it typically ties itself to be run by the default JVM at the time of the Eclipse install. This means that a discrepancy in JVMs will occur is a later version of the JVM is installed later. The problem can still occur even if the later version of the JVM is installed before Eclipse if the older JVM remains the default JVM.
To check the JVM version under which the Eclipse app is running:
- Open The "About Eclipse" dialog and click the "Installation Details" button.
- In the "Installation Details" window, click the "Configuration" tab.
- In the very long configuration listing, typically closer to the top, look for a line that says "
- The next line is the JVM that runs Eclipse
- Windows: The latest JDK installations update the "javapath" symlink under "C:\Program Files\Common Files\Oracle\Java" to point to the latest JVM installed. This helps keep Eclipse in Windows running on the latest JVM.
libjvm.dylib" may be called "
libjli.dylib" in newer JDKs.
Sometimes between the operating system and Eclipse, signals get crossed and Eclipse uses the wrong JVM (Java Virtual Machine, aka Java Run-time Engine/JRE) when it runs. This can cause a multitude of confusing problems such as the inability to run some plug-ins (e.g. "incorrect version number in plug-in class file" error). Here are some directions on how to manually configure Eclipse's initialization file to force it to use the proper JVM: http://wiki.eclipse.org/Eclipse.ini
In a nutshell (see the above link for details and official instructions!), one needs to configure the
-vm option in the
Show package contents" and browse down to
eclipse.inifile with a text editor.
-vmargsentry! Then add the next line which is the location of the latest installed JVM
Typical JVM installation locations:
-vmis set to "
C:\Program Files\Common Files\Oracle\Java\javapath\javaw.exe", then a -vm entry in the
eclipse.inifile may not be needed.
libjvm.dylib" or "
libjli.dylib" (newer JDKs).
REMEMBER: The configuration of what JVM runs the Eclipse app is a separate setting than the JVM to which developer code is compiled (the "compliance level" of the compiler) and the JRE used to run developer code (installed JRE). These settings can be found under "
One should regularly update Eclipse to make sure that you have the latest versions for Eclipse and all the plugins.
To manage update sites:
If you followed the directions below to install your plugins, the update sites should already be in Eclipse. To add new update sites or to check that you have the ones for the installed plugins,
To manually perform an update:
To perform a major release update on Eclipse:
RECOMMENDED: Force Eclipse to always update to the latest major release:
Or, you can explicitly add the update site for the new release (see above), whose name depends on the release, but is typically something on the order of
Once you add the update site for the new release, you can manually run the update as described above. On Windows machines, updating Eclipse itself will may require running Eclipse as an administrator (symptom: You get are unable to select the update due to "insufficient access privileges" or the like.)
For more information, see the documentation: FAQ How do I upgrade Eclipse?
Window Users: Note that updates to Eclipse itself may require that Eclipse be "run as administrator". Note that when Eclipse restarts after an installation, it is still running as as administrator. To return to normal operation, exit Eclipse completely and then run it again as normal.
UML Lab Home page: http://www.uml-lab.com/en/uml-lab/
UML Lab is a commercial UML diagramming tool for Eclipse that supports round-trip engineering, i.e. creating diagrams from code and creating code from diagrams.
Rice owns a license key for the full UML Lab functionality. The course staff will tell you how to obtain this key. The only restriction for the key is that it must be installed while on-campus and one must periodically (~ every 2 weeks) bring UML Lab up while on campus so it can renew its license.
A free but reduced functionality "Student Version" is available via their academic program: http://www.uml-lab.com/en/uml-lab/academic/. This version is has no limitations with regards to being on-campus.
UML Lab runs slightly differently than the other UML diagramming tools. Be sure to check out the Using UML Lab page.
UML Lab Floating License Notes:
Subclipse Home page: https://github.com/subclipse/subclipse/wiki
Subclipse provides Subversion source control capabilitiees for Eclipse to enable multi-developer access to a common, versioned source code repository. It is also used as the assignment turn-in mechanism in the course.
Subversion home page: http://subversion.apache.org/
Windows Users: Do not use "Run as administrator" to install Subclipse (see below)
Core SVNKit Library (required)
Optional JNA Library (recommended)
Subclipse(note that this automatically selects installing the SVNKit, which Mac and Linux users may need)
Subclipse - JavaHL Windows Binaries(Windows users only)
Subclipse - Maven Integration(Only if you intend to use Maven in other work -- not used in this class)
Linux and Mac Issues:
Linux and Macs have some known problems with recognizing and/or interoperating with the JavaHL component of Subclipse. JavaHL is a system-dependent Subversion client that either comes with Subclipse (usually only for Windows installations) or is already installed in the operationg system (typical of Macs and Linux). This is often caused by the latest stable SVN client version for that OS platform being incompatible with the latest Subclipse version.
The first thing to try if the above installation does not work, is the following work-around, which uses a pure-Java SVN client called "SVNKit":
If Subclipse was installed using "Run as administrator", the SVN operations may not be possible because no SVN client is available. See Preferences/Team/SVN to see what the "default SVN client" is set to and what options are available. The correct client for Windows is the JavaHL client.
The problem does not seem to appear if Subclipse is installed without "Run as administrator".
To fix the problem, uninstall all of Subclipse(see below) and reinstall it.
Sometimes, you need to completely uninstall Subclipse and start over. To uninstall Subclipse, go to Help/Installation Details.
There are many pieces to Subclipse, which need to be uninstalled one by one, though you do not need to restart Eclipse between each uninstall, only after the last one. Uninstall the following, the details of which will depend on what you initially installed:
Once everything is uninstalled, restart Eclipse (not as administrator) and reinstall Subclipse.
If no SVNKit is available, try the following solutions:
Mac OS X
If neither the regular installation above nor the SVNKit installation above works, you can try the following as a last resort:
Information about JavaHL on Mac OS X: https://github.com/subclipse/subclipse/wiki/JavaHL-on-OSX
Information on JavaHL on Linux: https://github.com/subclipse/subclipse/wiki/JavaHL-on-Linux
How to Use Subclipse
As of 9/2019, WindowBuilder is not currently bundled with Eclipse, so it needs to be will need to be explicitly installed.
WindowsBuilder is not included in the Java EE version of Eclipse, so if you must use the EE version (NOT recommended!) then you must manually install WindowBuilder.
WindowBuilder home page: http://www.eclipse.org/windowbuilder/
WindowBuilder is a (free!) What-You-See-Is-What-You-Get ("WYSIWG") editor for creating graphical user interfaces ("GUI"'s) in Java. The use of a an automated GUI builder such as WindowBuilder greatly simplifies and speeds up the development of GUI-based applications.
How to Use WindowBuilder
CodeTogether home page: https://www.codetogether.com/
CodeTogether is a tool that enables a "host" to share an Eclipse session with multiple remote users where everyone in the session can
For detailed installation directions, see https://www.codetogether.com/docs/codetogether-for-eclipse-installation/
How to use CodeTogether
This plugin is useful for those who wish to do web development using Eclipse. In particular, one of the few free WYSIWYG ("What You See Is What You Get") HTML editors is available here.
WTP Home Page: http://www.eclipse.org/webtools/
Update site: http://download.eclipse.org/webtools/repository/[eclipse_version]/ e.g. http://download.eclipse.org/webtools/repository/neon/
To get just the "Web Page Editor":
This plugin is only needed if you are doing Google App Engine development in Eclipse, particularly in Java. This tool includes the Google App Engine SDK and local emulator plus deployment tools.
Note that as of 8/15/16, the Google Plugin above only supports Java development for Google App Engine, not Python, Php or Go. To develop in these languages, you need install the stand-alone SDKs for those languages.
Google Plugin for Eclipse home page: https://developers.google.com/eclipse/
Update site: https://dl.google.com/eclipse/plugin/[version] e.g. https://dl.google.com/eclipse/plugin/4.6 (check for the latest version in the home page first)
This plugin is used for Python development in Eclipse.
PyDev home page: http://pydev.org
Update site: http://pydev.org/updates/
© 2020 by Stephen Wong