# Eclipse IDE

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

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

Attention

openHAB development requires Java JDK version 11.
Download the "Eclipse Installer": can be downloaded from the Eclipse web site
Launch the Installer and on the menu on the top right (3 bars)
Select ADVANCED MODE...
Select Eclipse IDE for Java Developers. Select Next >.

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.

select projects

Selection	Install if	Branches
openHAB Development	Debug/Demo Environment (Required)	2.5.x, 3.0
openHAB Add-ons	Add-ons Development	2.5.x, 3.0
openHAB ZigBee Binding	ZigBee Binding Development	2.5.x, 3.0
openHAB Z-Wave Binding	Z-Wave Binding Development	2.5.x, 3.0
openHAB BACNet Binding	BACNet Binding Development
openHAB Web UIs	Web UIs Development	2.5.x, 3.0
openHAB Core Framework	Core Framework Development	3.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.

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.
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.
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.
After all tasks are finished you are ready to start developing.
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 PaperUI 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:

|- org.openhab.demo.app
|--- runtime
|------- conf             Here you configure the manual text files
|------- userdata         Here is the openHAB user data
|------- logback.xml      XML file for logging options
|--- app.bndrun           The file to start OpenHAB
|--- pom.xml              The pom file with all dependencies for the demo project

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:

    <dependency>
    <groupId>org.openhab.addons.bundles</groupId>
    <artifactId>org.openhab.binding.astro</artifactId>
    <version>${project.version}</version>
    <scope>runtime</scope>
    </dependency>

To run the add-on with the app.bndrun run configuration. Double click to open app.bndrun file (takes a few seconds):
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.
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.
Start openHAB from the IDE by clicking "Run OSGi" (upper right of the app.bndrun window).
You can check that openHAB is running with your browser by going to: http://localhost:8080/paperui/ (the last / is important!)
You can check log output in the Console tab at the bottom.
Check the chosen binding is active in Paper UI > Configuration > Bindings

View all the above steps in a single animation:

Debug 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.

Install Sources

Sources are installed by cloning the openHAB Add-ons repository. If you select openHAB Add-ons during installation the installer automatically clones the openHAB Add-ons repository into git\openhab-addons under your installation folder.

If you didn't install openHAB Add-ons you can manually clone the openHAB Add-ons 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.
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. git\openhab-addons\bundles\org.openhab.binding.astro under the installation folder) as the root folder in the wizard.
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. .m2\repository\org\openhab\addons\bundles\org.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. git\openhab-addons\bundles\org.openhab.binding.astro\target 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