Eclipse on Linux

For years, serious ABAP development was almost synonymous with Windows. The classic SAP GUI dominated the landscape, and Linux users were often left experimenting on the sidelines.

That’s no longer the case.

With ABAP Development Tools (ADT) running inside Eclipse, Linux has become a fully viable — and in many cases superior — development environment. But there’s a catch: the setup isn’t entirely straightforward. Modern Linux distributions, Java modularization, and Wayland introduce a few sharp edges.

Here’s how to get it right.

Step 1: Start with the Right JDK

Eclipse and ADT are Java-based, so everything starts with a proper JDK.

The safest option for SAP-related tooling is SapMachine, SAP’s own OpenJDK distribution.

Download the latest version (tested with 21.0.6):

https://sapmachine.io/

SapMachine aligns closely with SAP’s internal validation stack, which reduces compatibility surprises.

Step 2: JavaFX — The Missing Dependency

If Eclipse launches but certain dialogs fail (especially embedded browser windows), the usual culprit is JavaFX.

Modern JDKs no longer bundle JavaFX by default.

Download the JavaFX SDK that exactly matches your JDK version:

https://gluonhq.com/products/javafx/

:::info Download the SDK version — not JMODs. :::

After downloading:

1. Extract the archive
2. Open the extracted folder
3. Copy everything inside its /lib directory
4. Paste it into your SapMachine JDK /lib directory

Yes — manual merging is currently the most reliable method.

If you prefer a shortcut:

:::info A pre-modified SapMachine JDK (with JavaFX merged) is available here:

https://share.kozlev.com/s/pFEn6yRK :::

Finally, move the completed JDK into:

1

sudo mv SapMachine-21 /usr/lib/jvm/

Optionally register it via update-alternatives if you manage multiple JDKs.

Step 3: Install Eclipse

Download Eclipse:

https://eclipseide.org/

During installation:

• Select the SapMachine JDK
• Install the standard Eclipse IDE package

At this point, Eclipse should start — but on modern Linux systems, you may hit the next obstacle.

Step 4: Wayland Rendering Issues

If you are running Wayland (default on Fedora, recent KDE, and GNOME setups), you might encounter:

• Blank login windows
• Flickering UI
• Rendering glitches
• Embedded browser failures

This is a known SWT/WebKit issue.

Fix #1: Modify eclipse.ini

Locate your eclipse.ini file and find:

1

-Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true

Add directly below:

1

-Dorg.eclipse.swt.internal.webkit.disableCompositingMode=true

Restart Eclipse.

For many setups, this resolves the issue immediately.

Fix #2: Force Eclipse to Use X11

If problems persist, run Eclipse under X11 instead of Wayland.

Edit your .desktop file and modify the Exec line:

1

Exec=env GDK_BACKEND=x11 SWT_GTK3=0 WEBKIT_DISABLE_COMPOSITING_MODE=1 <PATH TO ECLIPSE>

On KDE, you can add these under Environment Variables in the application configuration.

It’s not elegant — but it works.

Step 5: Install ABAP Development Tools (ADT)

With Eclipse stable, install ADT using SAP’s official guide:

https://developers.sap.com/tutorials/abap-install-adt..html

After installation, you gain:

• Modern ABAP editor
• CDS support
• Debugging
• Transport integration
• Seamless backend connectivity

All running natively on Linux.

Optional but Recommended: Dark Mode

Open Eclipse Marketplace and install:

Darkest Dark Theme

Long ABAP sessions are far more comfortable with a proper dark UI.

The Bigger Shift

ABAP development on Linux is no longer experimental. With SapMachine properly configured, JavaFX merged, and Wayland handled, Eclipse becomes a stable, production-grade environment.

For developers working on:

• S/4HANA
• ECC systems
• SAP NPL
• RISE or GROW landscapes

Linux is not just viable — it’s efficient.

The only real difference between a smooth setup and a frustrating one lies in a few undocumented details.

Now you know them.