Eclipse Ide

  • Navigation
  • Main Page
  • Community portal
  • Current events
  • Recent changes
  • Random page
  • Help

The Eclipse Foundation - home to a global community, the Eclipse IDE, Jakarta EE and over 375 open source projects, including runtimes, tools and frameworks. An Eclipse EMF model for enforcing profiles of project-specific settings (driven by the predicates model). An Eclipse EMF model for inducing dynamic working sets (driven by the predicates model). An Eclipse EMF model for managing modular PDE target platforms (based on composable targlets). An Eclipse EMF model for describing IDE configurations.

  • Toolbox
  • Page information
  • Permanent link
  • Printable version
  • Special pages
  • Related changes
  • What links here

Installing Eclipse is relatively easy, but does involve a few steps and software from at least two different sources. Eclipse is a Java-based application and, as such, requires a Java Runtime Environment or Java Development Kit (JRE or JDK) in order to run.

Note that on recent versions of Mac, a full JDK needs to be installed, not just a JRE; see instructions below.

Install a JVM

The latest release of Eclipse requires a 64-bit JVM, and does not support a 32-bit JVM.


Current releases of Eclipse require Java 11 JRE/JDK or newer.

Eclipse Ide Tutorial


If you are using Eclipse to do Java development, or are on macOS, install a JDK.In all cases, Eclipse requires a 64-bit JVM

A Java Development Kit (JDK) includes many useful extras for Java developers including the source code for the standard Java libraries.


Regardless of your operating system, you will need to install some Java virtual machine (JVM). You may either install a Java Runtime Environment (JRE), or a Java Development Kit (JDK), depending on what you want to do with Eclipse. If you intend to use Eclipse for Java development, then you should install a JDK. If you aren't planning to use Eclipse for Java development and want to save some disk space, install a JRE.

  • If you're using Windows, you may already have a JRE installed, but upgrading usually won't hurt.
  • If you're using Mac, and you don't have a JDK installed, you may get a bogus message from the OS stating that you should 'install the legacy Java SE 6 runtime'. Installing that will not solve the problem, because recent versions of Eclipse require a higher version. If you install just a JRE, and not a full JDK, that error message will persist. You must install a full JDK.
  • If using Linux, read this
    • GCJ will NOT work.

Eclipse 4.19 (2021-03)

Eclipse 4.19 (2021-03) was released on March 17, 2021. It is the supported release.

A Java 11 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2021-03 packages based on Eclipse 4.19, with certain packages choosing to provide one by default. The Installer now includes a JRE. Consider using the Installer. Please see 5 Steps to Install Eclipse.

Eclipse 4.18 (2020-12)

Eclipse 4.18 (2020-12) was released on December 16, 2020.

A Java 11 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2020-12 packages based on Eclipse 4.18, with certain packages choosing to provide one by default. The Installer now includes a JRE. Consider using the Installer. Please see 5 Steps to Install Eclipse.

Eclipse 4.17 (2020-09)

Eclipse 4.17 (2020-09) was released on September 16, 2020.

Consider using the Installer. Please see 5 Steps to Install Eclipse.

A Java 11 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2020-09 packages based on Eclipse 4.17, as well as the Installer.

Eclipse 4.16 (2020-06)

Eclipse 4.16 (2020-06) was released on June 17, 2020.

Consider using the Installer. Please see 5 Steps to Install Eclipse.

A Java 8 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2020-06 packages based on Eclipse 4.16, as well as the Installer.

Eclipse 4.15 (2020-03)

Eclipse 4.15 (2020-03) was released on March 18, 2020.

A Java 8 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2020-03 packages based on Eclipse 4.15, as well as the Installer.

Eclipse 4.14 (2019-12)

Eclipse 4.14 (2019-12) was released on December 18, 2019. See Eclipse 2019-12 schedule.

Consider using the Installer. Please see 5 Steps to Install Eclipse.

A Java 8 or newer JRE/JDK is required to run all Eclipse 2019-09 packages based on Eclipse 4.14, as well as the Installer.

Eclipse 4.13 (2019-09)

Eclipse 4.13 (2019-09) was released on September 18, 2019. See Eclipse 2019-09 schedule.

Consider using the Installer. Please see 5 Steps to Install Eclipse.

A Java 8 or newer JRE/JDK is required to run all Eclipse 2019-09 packages based on Eclipse 4.13, as well as the Installer.

Eclipse 4.12 (2019-06)

Eclipse 4.12 (2019-06) was released on June 19, 2019. See Eclipse 2019-06 schedule.

Consider using the Installer. Please see 5 Steps to Install Eclipse.

A Java 8 or newer JRE/JDK is required to run all Eclipse 2019-03 packages based on Eclipse 4.12, as well as the Installer.

Eclipse 4.11 (2019-03)

Eclipse 4.11 (2019-03) was released on March 20, 2019. See Eclipse 2019-03 schedule.

Consider using the Installer. Please see 5 Steps to Install Eclipse.

A Java 8 or newer JRE/JDK is required to run all Eclipse 2019-03 packages based on Eclipse 4.11, as well as the Installer.

Eclipse 4.10 (2018-12)

Eclipse 4.10 (2018-12) was released on December 20, 2018. It is the supported release. See Eclipse 2018-12 schedule.

Consider using the Installer. Please see 5 Steps to Install Eclipse.

A Java 8 or newer JRE/JDK is required to run all Eclipse 2018-12 packages based on Eclipse 4.10, including running the Installer. The reasoning behind requiring Java 8 are discussed here.

Eclipse 4.9 (2018-09)

Eclipse 4.9 (2018-09) was released on September 19, 2018. See Eclipse 2018-09 schedule.

A Java 8 or newer JRE/JDK is required to run all Eclipse 2018-09 packages based on Eclipse 4.9, including running the Installer. The reasoning behind requiring Java 8 are discussed here.

Eclipse Ide

Eclipse 4.8 (Photon)

Eclipse 4.8 (Photon) was released on June 27, 2018. See Photon schedule.

A Java 8 or newer JRE/JDK is required to run all Oxygen packages based on Eclipse 4.7, including running the Installer. The reasoning behind requiring Java 8 are discussed here.

Eclipse 4.7 (Oxygen)

Eclipse 4.7 (Oxygen) was released on June 28, 2017. See Oxygen schedule.

A Java 8 or newer JRE/JDK is required to run all Oxygen packages based on Eclipse 4.7, including running the Installer. The reasoning behind requiring Java 8 are discussed here.

Eclipse 4.6 (Neon)

Eclipse 4.6 (Neon) was released on June 22, 2016. See Neon schedule.

A Java 8 JRE/JDK is required to run all Neon packages based on Eclipse 4.6, including the Installer. The reasoning behind requiring Java 8 are discussed here.

Eclipse 4.5 (Mars)

Eclipse 4.5 (Mars) was released on June 24, 2015.

A Java 7 JRE/JDK is required for all Mars package downloads based on Eclipse 4.5, including the Installer. Information concerning tested configurations for Eclipse 4.5 is provided here.

Eclipse 4.4 (Luna)

Eclipse 4.4 (Luna) was released on June 25, 2014.

A Java 7 JRE/JDK is required for most of the Luna package downloads based on Eclipse 4.4. Information concerning tested configurations for Eclipse 4.4 is provided here.

Eclipse 4.3 (Kepler)

Eclipse 4.3 (Kepler) was released in June 2013.

A Java 6 JRE/JDK is recommended for Eclipse 4.3. More information concerning tested configurations for Eclipse 4.3 is provided here.


JRE/JDK Sources

Be sure to install a JVM with the same bit level as Eclipse
i.e. install a 32-bit JRE to run 32-bit Eclipse; install a 64-bit JRE to run 64-bit Eclipse

There are several sources for a JRE/JDK. Here are some of the more common/popular ones (listed alphabetically):

Eclipse Ide Donwload

Download Eclipse

Download Eclipse from the Eclipse Downloads Page.

There are several package choices. Note that you can install the features from any package into any other package. If you are, for example, planning to do mostly Java development and some C/C++ development, you should download the Eclipse IDE for Java Developers and then add the C/C++ development tools via the 'Help > Install New Software...' menu option.

The download will be delivered as a compressed (i.e. a '.zip', or '.tar.gz') file. Decompress this file into the directory of your choice (e.g. 'c:eclipse' on Windows) and ensure you have full Read and Execute permissions. You can optionally create a shortcut of the executable file ('eclipse.exe' on Windows, or 'eclipse' on Linux).

Note that there is a known problem with the built-in decompression utility on all current versions of Windows. We recommend that you use a more robust decompression utility such as the open source 7zip when decompressing an Eclipse download. Some people report success when initially decompressing Eclipse into a root directory (e.g. c:) and then moving it to a more appropriate home (e.g. c:Program FilesEclipse)

Configure Eclipse to use the JVM

It is strongly recommended to configure Eclipse with the specific JVM that you want. See the instructions at Eclipse.iniThis is a very important step to be sure that Eclipse is using the JVM you intend and can't be influenced by any other software that might alter your system.The JVM used to launch Eclipse has no affect on whether it can compile Java sources for other Java language versions.

Extending Eclipse

Use the Help > Install new software... menu option to add Kepler features to your Eclipse installation (you can, for example, use this option to add C/C++ development support). Additionally, you can tap into a vast collection of extensions provided by the Eclipse community and ecosystem via the Eclipse Marketplace Client (Help > Eclipse Marketplace). Note that not all Eclipse packages contain the Eclipse Marketplace Client.

Troubleshooting

Java was started but returned exit code = 13

If you've 'installed' Eclipse but are having trouble getting it to run, the most likely cause is that you have not correctly specified the JVM for it to run under. You may need to edit the eclipse.ini file.

Another common mistake on Microsoft Windows is a mismatch between the 'bittedness' of Eclipse and the JVM/JDK. This is the most frequent cause of an Error 13. 64-bit Eclipse requires a 64-bit JVM, and 32-bit Eclipse requires 32-bit JVM--you can not mix-and-match between 32-bit and 64-bit, so make sure the version of Eclipse you installed matches the JVM/JDK that you're using to run it (and make sure you're using eclipse.ini to specify the exact JVM used to run Eclipse, described above).

As a simple test, open a Command Prompt window, move to the directory that is pointed to by the -vm argument in your eclipse.ini, and run the intended java.exe with the -d32 switch to test if it supports 32-bit, or -d64 to test for 64-bit support. It's often simplest to download a version of Eclipse that will work with whatever Java you already have installed.

To open 'Eclipse' you need to install the legacy Java SE 6 runtime

Eclipse Ide Neon Download For Windows 10

On more recent versions of the Mac, if you don't have a full JDK of an appropriately high version installed, the OS produces this bogus message. Installing any JRE will not eliminate this problem. A full JDK needs to be installed on the Mac.

Download Eclipse Org

Extraction requires a password or otherwise fails on Windows.

Eclipse downloads are not password protected. This is a known problem with the built-in decompression utility on all current versions of Windows. We recommend that you either download the installer or use a more robust decompression utility such as the open source 7zip when decompressing an Eclipse download. Some people report success when initially decompressing Eclipse into a root directory (e.g. c:) and then moving it to a more appropriate home (e.g. c:Program FilesEclipse)

Eclipse Ide Download

More information

Retrieved from 'http://wiki.eclipse.org/index.php?title=Eclipse/Installation&oldid=442664'

Eclipse is the development environment used since the inception of openHAB.To make development easier an out-of-the-box setup is available that completely configures Eclipse to easily develop for the openHAB projects.This guide describes the steps to setup Eclipse and how to run and debug an add-on in Eclipse.

Existing Eclipse Installations

If you already have Eclipse installed it is recommended to perform a separate Eclipse install for OpenHAB to avoid overriding your existing Eclipse configuration.

# Eclipse IDE Setup

  1. Install the Java 11 JDK if you did not have it installed.

    Attention

    openHAB development requires Java JDK version 11.

  2. Download the 'Eclipse Installer': can be downloaded from the Eclipse web site(opens new window)

  3. Launch the Installer and on the menu on the top right (3 bars)

  4. Select ADVANCED MODE...

  5. Select Eclipse IDE for Java Developers. Select Next >.

  6. Under GitHub Projects > openHAB select openHAB Development and any desired option from openHAB Add-ons (includes all add-ons from openhab-addons repo), openHAB ZigBee Binding or openHAB Z-Wave Binding.

    SelectionInstall ifBranches
    openHAB DevelopmentDebug/Demo Environment (Required)2.5.x, 3.0
    openHAB Add-onsAdd-ons Development2.5.x, 3.0
    openHAB ZigBee BindingZigBee Binding Development2.5.x, 3.0
    openHAB Z-Wave BindingZ-Wave Binding Development2.5.x, 3.0
    openHAB BACNet BindingBACNet Binding Development
    openHAB Web UIsWeb UIs Development2.5.x, 3.0
    openHAB Core FrameworkCore Framework Development3.0

    Attention

    Select 2.5.x if you want to develop for 2.5.x.The Core Framework only has a master branch (3.0 development), which means you can no longer make Core Framework changes for a 2.5.x system.

  7. Click Next>, verify/modify Root and install folder name. Click on Show all variables to open the window shown below.

    Explanation of some of the variables

    • Root install folder: The base folder where the Installation folder will be placed.
    • Installation folder name: This is the directory in the root install folder everything will be installed in.
    • GitHub user ID: This is your GitHub user name used to configure the cloned Git projects.
  8. Click Next> and Finish to start installation.

    During install accept licence agreement, 'Unsigned Content' for Bndtools, and Eclipse Foundation certificates when requested to complete IDE installation.

  9. At this point the Eclipse installer is finished and the Eclipse IDE is automatically launched to continue the installation process.

    Attention

    It is important, during the first Eclipse IDE launch, to leave Eclipse open until all openHAB related initial Setup tasks / Download sources / Builds are completed.

    Setup tasks will personalize the IDE with openHAB code formatting tools, configurations and a demo app.Setup tasks will also download openHAB latest projects you have selected during installation. Like openhab-distro and the add-ons openhab-addons project if you have selected it.

    Click bottom right button in the IDE for Progress.

  10. After all tasks are finished you are ready to start developing.

  11. If you need additional libraries see the Build System documentation.For other libraries supported out-of-the-box check the Default Libraries on the guidelines page.

# Working with Add-ons

To easily run, modify and debug an add-on the openHAB Development setup installs and imports a demo project that contains a complete openHAB environment to run and debug an add-on.This mechanism replaces the add-on installation process via the UI that you would use outside the IDE.

# Running Add-ons

Under Infrastructure you will find the project org.openhab.demo.app.This project contains the full configuration to run OpenHAB.The following files are of interest for the execution environment:

  1. To let the demo project know about the add-on, the add-on must be added to the demo project pom.xml.Here is an example for the astro binding:

  2. To run the add-on with the app.bndrun run configuration.Double click to open app.bndrun file (takes a few seconds):

  3. Under Browse Repos search for the add-on you want to run (astro in our case) and add it to the Run Requirements list using drag&drop from the Browse Repos list:

    TIP

    If you cannot find the binding you want run/debug in the Browse Repos list, or the list is empty,then it is likely either the pom.xml of the demo project contains an error or there is a build problem with your project.Check if your project has no compile errors.Or run Maven on the command line to check if it reports any errors.

  4. Save and click 'Resolve': a window with the list of resolved bundles will be shown.Click Finish and save the file.

    TIP

    Watch out - it's easy to miss saving the app.bndrun file.If you see the little asterisk next to app in the app tab you haven't yet saved.

    Now the IDE is ready to start openHAB with a minimum set of the openHAB core bindings, UIs and the add-ons you configured.

  5. Start openHAB from the IDE by clicking 'Run OSGi' (upper right of the app.bndrun window).

  6. You can check that openHAB is running with your browser by going to: http://localhost:8080/ (the last / is important!)

  7. You can check log output in the Console tab at the bottom.

  8. Check the chosen binding is active in UI > Settings > Bindings

Eclipse ide

View all the above steps in a single animation:

# Modifying and Debugging Add-ons

If you don't just want to run an add-on, but also want to modify and debug it you need to install sources for the add-on and build them locally.

  1. Install Sources

    Sources are installed by cloning the openHAB Add-ons(opens new window) repository.If you select openHAB Add-ons during installation the installer automatically clones the openHAB Add-ons(opens new window) repository into gitopenhab-addons under your installation folder.

    If you didn't install openHAB Add-ons you can manually clone the openHAB Add-ons(opens new window) repository by executing git clone https://github.com/openhab/openhab-addons.git in the git folder under your installation folder.

    You can now modify add-on sources as needed.

  2. Build Sources

    Add the add-on as an Eclipse project so that Eclipse will build it automatically.Import the add-on project via File > Import... > Maven > Existing Maven Projects.Specify your add-on's source root folder (e.g. gitopenhab-addonsbundlesorg.openhab.binding.astro under the installation folder) as the root folder in the wizard.

  3. Start a Debug Session

    Simply start your debug session by clicking 'Debug OSGi' (upper right of the app.bndrun window).You can now use breakpoints and all other Eclipse debug tools.

Where do add-on jar files come from?

If you just run an add-on following the above steps then the required add-on jar files are retrieved through your Maven repository folder .m2/repository (e.g. .m2repositoryorgopenhabaddonsbundlesorg.openhab.binding.astro).If you imported your add-on as a project then the jar file is no longer retrieved from the Maven repository, but instead from the project build (e.g. gitopenhab-addonsbundlesorg.openhab.binding.astrotarget under the installation folder).

# Using New Bindings

If you want to develop a new binding read about the Skeleton Script to generate the base for your binding and create all required files.Then follow the above steps to build your sources and to configure the demo app to run your binding.

# Updating OpenHAB

You can update the OpenHAB version you are running in the IDE at any time simply by updating your git repos under your install folder.For example to update to the latest version run git checkout in each repo folder under your git folder in the installation folder.

Caught a mistake or want to contribute to the documentation? Edit this page on GitHub(opens new window)