Eclipse IDE



There are generally three ways to install Eclipse:

Also see the official installation guide.

Recommended installation locations

On Linux:

  • /home/shadylady/tools/eclipse/eclipse-java
  • /opt/eclipse (according to Linux#Manualsoftwareinstallation)
  • /usr/lib/eclipse  (This is only if installed by an official system package manager)
  • /snap/eclipse/current  (If installed via snap )

On Windows:

  • C:\ProgramData\eclipse\eclipse-java 

The Eclipse INI Configuration File

Eclipse is launched with settings specified in an INI file in the installation directory called eclipse.ini. See the official eclipse.ini documentation. Changes to the INI file will take effect upon the next restart of Eclipse.

When Eclipse is installed via snap

There is no way to edit eclipse.ini directly when Eclipse is installed via snap. Workarounds include:

  • Use the --launcher.ini /path/to/eclipse.ini option.
  • Pass individual settings e.g. -vmargs -Xms1g -Xmx3g  to the launcher.

One alternative way to modify snap installs is through MenuLibre:

Follow these instructions to install MenuLibre:

sudo apt-get update
sudo add-apt-repository ppa:menulibre-dev/daily
sudo apt-get install menulibre

Now follow these instructions to modify eclipse.ini:

  1. Copy /snap/eclipse/current/eclipse.ini to somewhere you can edit it. Let us say, copy it to /home/USERNAME/eclipse.ini.

  2. Edit the arguments you want to update and save the file.

  3. Open Menulibre

  4. Search for "Eclipse."

  5. Click in the Eclipse icon.

  6. In the "Command" input, add the --launcher.ini option after the binary path. In our example, we would replace

     /snap/bin/eclipse %f


     /snap/bin/eclipse %f --launcher.ini /home/USERNAME/eclipse.ini 
  7. Click in Menulibre's "Save" button.


Selecting a JVM

Eclipse 2020+ requires to run with a Java 11 VM or higher.  If you need to set which JRE Eclipse runs with, add the following lines to the eclipse.ini.



It is not recommended to put your code in a workspace directory. A "workspace" in Eclipse is more akin to isolated or "portable" application settings; not a place to store projects.

It is highly discouraged to put code in an Eclipse workspace folder.

Potential workspace locations:

  • ~/tools/eclipse/workspace    (Linux)
  • ~/.config/eclipse/workspace 
  • C:\ProgramData\eclipse\workspace      (Windows)


Application memory

Eclipse will perform terribly unless you give it a few GB of memory (RAM).

Ensure the eclipse.ini contains the following JVM options:


The values above are just an example. Scale them to fit your needs.

Create a desktop launcher

If Eclipse was installed manually, you'll want to create a desktop application launcher or shortcut. See Linux#Desktopentries.

An example eclipse.desktop  file in Linux you could put in ~/.local/share/applications/:

[Desktop Entry]
Comment=Java Development Environment

Disable Welcome menu

To disable the Welcome menu from consuming the full application screen on startup:

  • Clear "Always show Welcome at start up" at the bottom right corner of the Welcome menu.

General settings

In Window > Preferences > General:

  • Set "Show heap status"

Editor settings

In Window > Preferences > General > Editors

Text Editors:

  • Set "Displayed tab width" to "3"
  • In "Spelling", clear "Enable spell checking"

Workspace settings

In Window > Preferences > General > Workspace:

  • Set "Refresh using native hooks or polling"
  • Set "Show full workspace path"
  • Set "Text file encoding" to "UTF-8"
  • Set "New text file line delimiter" to "Unix"

Expand Workspace > Build.  Set "Save automatically before build"

Gradle settings

Default Gradle settings in Eclipse are currently broken so you must "Override workspace settings" every time. See Github issue.

In Window >Preferences > Gradle:

Java settings

In Window > Preferences > Java:

Code Style > Formatter:

Compiler > Error/Warnings > Deprecated and restricted API:

  • Set "Forbidden reference (access rules)" to "Ignore"

Editor > Content Assist > Favorites:

  • Click "New Type..." and add "org.junit.jupiter.api.Assertions"


In Editor > Templates:


Create some updated templates for LogTools, JUnit 5, etc.

Set up Installed JREs

See also the page on Java.

In Java > Installed JREs, add any manually installed JREs. (i.e. Zulu in the /opt/zulu directory)

Check to make sure the jfxrt.jar is present for JavaFX to work.

In the "Edit JRE" dialog, expand the *.jar entries and check if a Source attachement is detected. These should be detected automatically.



To get JavaFX to work in Eclipse, a plugin is presently required. Follow the instructions to install e(fx)clipse:

  1. Go to Help > Eclipse Marketplace...
  2. Then search and install efxclipse

ANSI Color Console

This plugin provides nice log level coloring in the console as supported by IHMC's Log Tools library.

Search "ansi console" in the Marketplace and install ANSI Escape in Console by Mihai Nita.

C++ development

CMake editor:

Eclipse file generator from CMake:


Install Egit:

Set Git default Pull to 'rebase' as described in Git Tips And Tricks

In Window > Preferences > Team > Git > History:

  • Set "Maximum characters to show for a tag" to 100
  • Set "Maximum characters to show for a branch" to 100

Importing Gradle Projects

Default Gradle settings in Eclipse are currently broken so you must "Override workspace settings" every time.

  1. Select File > Import...
  2. Select the "Gradle > Existing Gradle Project" import wizard
  3. Clear "Show the welcome page the next time the wizard appears"
  4. Set the "Project root directory"
  5. Select "Override workspace settings"
    1. Set "Gradle distribution" to "Local installation directory" and point to your local Gradle installation
      (Common locations are /usr/share/java/gradle, /opt/gradle, and C:\gradle)
    2. Set "Show Console View"
    3. Set "Show Executions View"
  6. (passive) Check that a tree populates on the "Import Preview" page

See Gradle#Troubleshooting

More info at


General troubleshooting steps for Eclipse are:

  • Project > Rebuild
  • Project > Clean...
  • Gradle > Refresh Gradle Project
  • File > Restart
  • Create a new workspace

Adding and removing projects from workspace

It might be best to delete projects in Eclipse before deleting them on disk. Else your workspace might get corrupted if you try to delete from the File Explorer.


Sometimes Eclipse will "forget" part of it's classpath. Recommended solution: Refresh Gradle Project

Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError: com/martiansoftware/jsap/JSAPException
	at java.lang.Class.getDeclaredMethods0(Native Method)
	at java.lang.Class.privateGetDeclaredMethods(
	at java.lang.Class.privateGetMethodRecursive(
	at java.lang.Class.getMethod0(
	at java.lang.Class.getMethod(
	at sun.launcher.LauncherHelper.validateMainClass(
	at sun.launcher.LauncherHelper.checkAndLoadMain(
Caused by: java.lang.ClassNotFoundException: com.martiansoftware.jsap.JSAPException
	at java.lang.ClassLoader.loadClass(
	at sun.misc.Launcher$AppClassLoader.loadClass(
	at java.lang.ClassLoader.loadClass(
	... 7 more

See also

TODO: How to run Gradle tasks with custom options

Learn more