From ArchWiki
(Redirected from Java (Italiano))

From the Wikipedia article:

Java is a programming language originally developed by Sun Microsystems and released in 1995 as a core component of Sun Microsystems' Java platform. The language derives much of its syntax from C and C++ but has a simpler object model and fewer low-level facilities. Java applications are typically compiled to bytecode that can run on any Java virtual machine (JVM) regardless of computer architecture.

Arch Linux officially supports the open source OpenJDK versions 8, 11, 17 and 21 — Long-Term Support (LTS) versions, and 22 — the latest released version. All these JVM can be installed without conflict and switched between using helper script archlinux-java (installed with java-runtime-common package). Several other Java environments are available in Arch User Repository but are not officially supported.


  • Arch Linux officially supports the OpenJDK implementations only.
  • After installation, the Java environment will need to be recognized by the shell ($PATH variable). This can be done by sourcing /etc/profile from the command line, by logging out/in again of the Desktop environment, or by rebooting.

Two common packages are respectively pulled as dependency, named java-runtime-common (containing common files for Java Runtime Environments) and java-environment-common (containing common files for Java Development Kits). The provided environment file /etc/profile.d/ points to a linked location /usr/lib/jvm/default/bin, set by the archlinux-java helper script.

Warning: The links /usr/lib/jvm/default and /usr/lib/jvm/default-runtime should always be edited with archlinux-java.

This is used to display and point to a working default Java environment in /usr/lib/jvm/java-${JAVA_MAJOR_VERSION}-${VENDOR_NAME} or a Java runtime in /usr/lib/jvm/java-${JAVA_MAJOR_VERSION}-${VENDOR_NAME}/jre.

Most executables of the Java installation are provided by direct links in /usr/bin/, while others are available in $PATH.

Warning: The script /etc/profile.d/ is no longer provided by any package.


OpenJDK is an open-source implementation of the Java Platform, Standard Edition (Java SE), designated as the official reference implementation. There are several distributors of OpenJDK builds such as Adoptium (formerly known as AdoptOpenJDK) and Amazon Corretto. The Arch Linux OpenJDK packages are built from the upstream OpenJDK source code.

Headless JRE
The minimal Java runtime - needed for executing non-GUI Java programs.
Full JRE
Full Java runtime environment - needed for executing Java GUI programs.
Java Development Kit - needed for Java development.

JDK, JRE, and JRE-headless conflicts with each other, as the smaller packages are subsets; i.e. JDK conflicts and provides JRE and JRE conflicts and provides JRE-headless.

Version Headless JRE Full JRE JDK Documentation Sources
OpenJDK 22 jre-openjdk-headless jre-openjdk jdk-openjdk openjdk-doc openjdk-src
OpenJDK 21 jre21-openjdk-headless jre21-openjdk jdk21-openjdk openjdk21-doc openjdk21-src
OpenJDK 17 jre17-openjdk-headless jre17-openjdk jdk17-openjdk openjdk17-doc openjdk17-src
OpenJDK 11 jre11-openjdk-headless jre11-openjdk jdk11-openjdk openjdk11-doc openjdk11-src
OpenJDK 8 jre8-openjdk-headless jre8-openjdk jdk8-openjdk openjdk8-doc openjdk8-src

OpenJDK GA — Latest OpenJDK General-Availability Release build from Oracle. || java-openjdk-binAUR

OpenJDK EA — Latest OpenJDK Early-Access build for development version from Oracle. || java-openjdk-ea-binAUR

IcedTea-Web — Java Web Start and the deprecated Java browser plugin. || icedtea-web


OpenJFX is the open-source implementation of JavaFX. You do not need to install this package if you are using Oracle JDK. This package only concerns users of the open source implementation of Java (OpenJDK project), and its derivatives.

Version Runtime and Development Documentation Sources
OpenJFX 21 java-openjfxAUR java-openjfx-docAUR java-openjfx-srcAUR
OpenJFX 17 java17-openjfxAUR java17-openjfx-docAUR java17-openjfx-srcAUR
OpenJFX 11 java11-openjfxAUR java11-openjfx-docAUR java11-openjfx-srcAUR
OpenJFX 8 java8-openjfxAUR java8-openjfx-docAUR java8-openjfx-srcAUR

OpenJFX GA — Latest OpenJFX General-Availability Release build from Gluon. || java-openjfx-binAUR

OpenJFX EA — Latest OpenJFX Early-Access build for development version from Gluon. || java-openjfx-ea-binAUR[broken link: package not found]

Other implementations

  • Oracle JDK — Oracle's commercially licensed build of OpenJDK. Note that some versions are only available via manual download, which requires to sign the OTN agreement and create an Oracle account. ||
JRE: jreAUR jre-ltsAUR jre11AUR jre8AUR jre7AUR
JDK: jdkAUR jdk-ltsAUR jdk11AUR jdk8AUR jdk7AUR
  • Eclipse Adoptium/Temurin — Eclipse's implementation of JRE/JDK, based on the Hotspot JVM (formerly AdoptOpenJDK). Note that the JRE is known as Eclipse Temurin. || jdk-temurinAUR jdk17-temurinAUR jdk11-temurinAUR
  • AWS Corretto — Amazon Web Services' distribution of OpenJDK. || amazon-corretto-8AUR amazon-corretto-11AUR amazon-corretto-17AUR amazon-corretto-21-binAUR amazon-corretto-221AUR[broken link: package not found]
  • OpenJ9 — Eclipse's implementation of JRE/JDK, based on the J9 JVM, contributed by IBM. || jdk-openj9-binAUR jdk17-openj9-binAUR jdk11-openj9-binAUR jdk8-openj9-binAUR
  • IBM Certified — IBM Semeru Runtime Certified Edition. || jdk11-j9-binAUR
  • IBM J9 — IBM's implementation of JRE, using OpenJ9 contributions. || jdk8-j9-binAUR jdk7-j9-binAUR jdk7r1-j9-binAUR
  • Microsoft OpenJDK — Microsoft's distribution of OpenJDK. || microsoft-openjdk-11-binAUR microsoft-openjdk-17-binAUR microsoft-openjdk-21-binAUR
  • Azul JDK — Azul's JDK implementations. Note that the Azul Zulu Builds of OpenJDK are open source, while The Azul Zulu Prime Builds of OpenJDK are a commercial product free for development and evaluation. ||
Zulu: zulu-8-binAUR zulu-11-binAUR zulu-17-binAUR zulu-21-binAUR
Zulu Prime: jdk17-zulu-prime-binAUR

Note: 32-bit versions of Oracle JDK can be found by prefixing bin32-, e.g. bin32-jreAUR. They use java32-runtime-commonAUR, which functions as java-runtime-common by suffixing with 32, e.g. java32. The same analogy applies to java32-environment-commonAUR, which is only used by 32-bit JDK packages.

Development tools

For integrated development environments, see List of applications/Utilities#Integrated development environments and the Java IDEs subsection specifically.

To discourage reverse engineering an obfuscator like proguardAUR can be used.


  • CFR — Java decompiler, supporting modern features of Java 9, 10 and beyond. || cfr
  • Fernflower — Analytical decompiler for Java, developed as part of IntelliJ IDEA. || fernflower-gitAUR
  • Vineflower — Java decompiler forked from Fernflower, aiming to improve code quality. Also available as an IntelliJ IDEA plugin. || vineflowerAUR
  • Krakatau — Java decompiler, assembler, and disassembler. || krakatau-gitAUR
  • Procyon decompiler — Experimental Java decompiler, inspired by ILSpy and Mono.Cecil. || procyon-decompiler
  • Java Decompiler (JD-Core) — Popular Java decompiler providing a GUI (see JD-GUI) and supporting Java 1-10. || jd-core-javaAUR
  • Jadx — Android DEX to Java decompiler with an optional GUI (see Jadx-GUI). || jadx
  • JAD — Unmaintained Java decompiler (last release 2006). || jad

GUI Frontends

  • Bytecode Viewer — Java reverse engineering suite, including a decompiler, editor and debugger; Frontend for CFR/Fernflower/Procyon || bytecode-viewerAUR
  • Recaf — An easy to use modern Java bytecode editor that abstracts away the complexities of Java programs; Frontend for CFR/Fernflower/Procyon || recaf-binAUR
  • Java Decompiler (JD-GUI) — Popular Java decompiler providing a GUI and supporting Java 1-10; Frontend for JD-Core || jd-guiAUR
  • Jadx-GUI — Android APK DEX to Java decompiler with an optional GUI; Frontend for Jadx || jadx
  • Luyten — An Open Source Java Decompiler Gui; Frontend for Procyon || luytenAUR

Switching between JVM

The helper script archlinux-java (package : java-runtime-common) provides such functionalities:

archlinux-java <COMMAND>

status          List installed Java environments and enabled one
get             Return the short name of the Java environment set as default
set <JAVA_ENV>  Force <JAVA_ENV> as default
unset           Unset current default Java environment
fix             Fix an invalid/broken default Java environment configuration

List compatible Java environments installed

$ archlinux-java status


$ archlinux-java status
Available Java environments:
   java-11-openjdk (default)

Note the (default) denoting that java-11-openjdk is currently set as default. Invocation of java and other binaries will rely on this Java install. Also note on the previous output that only the JRE part of OpenJDK 8 is installed here.

Change default Java environment

# archlinux-java set <JAVA_ENV_NAME>


# archlinux-java set java-8-openjdk/jre
Tip: To see possible <JAVA_ENV_NAME> names, use archlinux-java status.

Note that archlinux-java will not let you set an invalid Java environment. In the previous example, jre8-openjdk is installed but jdk8-openjdk is not so trying to set java-8-openjdk will fail:

# archlinux-java set java-8-openjdk
'/usr/lib/jvm/java-8-openjdk' is not a valid Java environment path

Unsetting the default Java environment

There should be no need to unset a Java environment as packages providing them should take care of this. Still should you want to do so, just use command unset:

# archlinux-java unset

Fixing the default Java environment

If an invalid Java environment link is set, calling the archlinux-java fix command tries to fix it. Also note that if no default Java environment is set, this will look for valid ones and try to set it for you. Officially supported package "OpenJDK 8" will be considered first in this order, then other installed environments.

# archlinux-java fix

Launching an application with the non-default java version

If you want to launch an application with another version of java than the default one (for example if you have both version 18 and 11 installed on your system), you can wrap your application in a small bash script to locally change the default PATH of java. For example if the default version is java 18 and you want to use java 11:


export PATH="/usr/lib/jvm/java-11-openjdk/bin/:$PATH"
exec /path/to/application "$@"

For a systemd service you can append JAVA_HOME to environment variables in the drop-in file:


Package pre-requisites to support archlinux-java

Note: This info also applies to archlinux32-java for 32-bit Java packages, with the proper inclusion of 32 to the package/executable names, where applicable.

This section is targeted at packagers willing to provide packages in the AUR for an alternate JVM and be able to integrate with the Arch Linux JVM scheme (i.e. to be compatible with archlinux-java); to do so, packages should:

  • Place all files under /usr/lib/jvm/java-${JAVA_MAJOR_VERSION}-${VENDOR_NAME }
  • Ensure all executables for which java-runtime-common and java-environment-common provide links are available in the corresponding package
  • Ship links from /usr/bin to executables, only if these links do not already belong to java-runtime-common and java-environment-common
  • Suffix man pages with -${VENDOR_NAME}${JAVA_MAJOR_VERSION} to prevent conflicts (see jre8-openjdk file list where man pages are suffixed with -openjdk8)
  • Do not declare any conflicts nor replaces with other JDKs, java-runtime, java-runtime-headless nor java-environment
  • Use script archlinux-java in install functions to set the Java environment as default if no other valid Java environment is already set (ie: package should not force install as default). See officially supported Java environment package sources for examples

Also please note that:

  • Packages that need any Java environment should declare dependency on java-runtime, java-runtime-headless or java-environment as usual
  • Packages that need a specific Java vendor should declare dependency on the corresponding package
  • OpenJDK packages now declare provides="java-runtime-openjdk=${pkgver}" etc. This enables a third-party package to declare dependency on an OpenJDK without specifying a version



Due to the fact that the JDBC-drivers often use the port in the URL to establish a connection to the database, it is considered "remote" (i.e., MySQL does not listen to the port as per its default settings) despite the fact that they are possibly running on the same host, Thus, to use JDBC and MySQL you should enable remote access to MySQL, following the instructions in MariaDB#Grant remote access.

IntelliJ IDEA

If IntelliJ IDEA outputs The selected directory is not a valid home for JDK with the system Java SDK path, you may have to install a different JDK package and select it as IDEA's JDK.

Impersonate another window manager

You may use the wmname from to make the JVM believe you are running a different window manager. This may solve a rendering issue of Java GUIs occurring in window managers like Awesome or Dwm or Ratpoison. This works because the JVM contains a hard-coded list of known, non-re-parenting window managers. For maximum irony, some users prefer to impersonate LG3D, the non-re-parenting window manager written by Sun, in Java. Try setting "compiz", "Metacity" or "LG3D".

$ wmname window_manager_name

You must restart the application in question after issuing the wmname command.

Alternatively, the javaagent JavaMatePatch, created to set the WM name in MATE and resolve the bug with java swing apps working incorrectly when launched in full screen, can be used. Add -javaagent:JavaMatePatch-1.0.0-SNAPSHOT.jar=window_manager_name to the java options to use it.

Illegible fonts

In addition to the suggestions mentioned below in #Better font rendering, some fonts may still not be legible afterwards. If this is the case, there is a good chance Microsoft fonts are being used. Install ttf-ms-fontsAUR.

Missing text in some applications

If some applications are completely missing texts it may help to use the options under #Tips and tricks as suggested in FS#40871.

Gray window, applications not resizing with WM, menus immediately closing

The standard Java GUI toolkit has a hard-coded list of "non-reparenting" window managers. If using one that is not on that list, there can be some problems with running some Java applications. One of the most common problems is "gray blobs", when the Java application renders as a plain gray box instead of rendering the GUI. Another one might be menus responding to your click, but closing immediately.

There are several things that may help:

See [1] for more information.

System freezes when debugging JavaFX Applications

If your system freezes while debugging a JavaFX Application, you can try to supply the JVM option -Dsun.awt.disablegrab=true.


JavaFX's MediaPlayer constructor throws an exception

Creating instance of MediaPlayer class from JavaFX's sound modules might throw following exception (both Oracle JDK and OpenJDK)

... (i.e. FXMLLoader construction exceptions) ...
Caused by: MediaException: UNKNOWN : Could not create player! : Could not create player!
 at <constructor call>

which is a result of some incompatibilities of JavaFX with modern ffmpeg build delivered within Arch Linux repository.

Working solution is to install ffmpeg-compat-55AUR. Alternatively, installing ffmpeg-compat-57AUR[broken link: package not found] may work if the previous version fails to build.


Java applications cannot open external links

If a Java application is not able to open a link to, for example, your web browser, install gvfs. This is required by the Desktop.Action.BROWSE method. See [2]

Error initializing QuantumRenderer: no suitable pipeline found

Possible issues / solutions:

Tips and tricks

Note: Suggestions in this section are applicable to all applications, using explicitly installed (external) Java runtime. Some applications are bundled with own (private) runtime or use own mechanics for GUI, font rendering, etc., so none of written below is guaranteed to work.

Behavior of most Java applications can be controlled by supplying predefined variables to Java runtime. From this forum post, a way to do it consists of adding the following line in your ~/.bash_profile (or /etc/profile.d/ to affect programs that are not run by sourcing ~/.bash_profile):

export JDK_JAVA_OPTIONS="-D<option 1> -D<option 2>..."

For example, to use system anti-aliased fonts and make swing use the GTK look and feel:

export JDK_JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true'

Three such variables exist, the options which are explained later in the table below take priority.

JAVA_TOOL_OPTIONS Affects applications as well as tools like javac or the jshell.
JDK_JAVA_OPTIONS Affects applications (everything started via the java command). Requires Java 9.
(command line options) Arguments specified before the "class name" argument are Java options.
_JAVA_OPTIONS The old way, affects applications and tools.

Better font rendering

Both closed source and open source implementations of Java are known to have improperly implemented anti-aliasing of fonts. This can be fixed with the following options: -Dawt.useSystemAAFontSettings=on, -Dswing.aatext=true

See Java Runtime Environment fonts for more detailed information.

Silence 'Picked up JDK_JAVA_OPTIONS' message on command line

Setting the JDK_JAVA_OPTIONS environment variables makes java (openjdk) write to stderr messages of the form: 'Picked up JDK_JAVA_OPTIONS=...'. To suppress those messages in your terminal you can unset the environment variable in your ~/.bashrc and alias java to pass those same options as command line arguments:

alias java='java "$SILENT_JAVA_OPTIONS"'

Non interactive shells, like the launcher scripts for Java programs, (usually) do not read the ~/.bashrc, but still inherited exported variables from their parent process (which in turn inherited it at some point from the login shell which read the ~/.bash_profile). As for the cases when they do, one put’s generally a statement at the op of the ~/.bashrc to avoid the file being read. That way, the variables are passed to programs launched via the desktop menu and in the case of an interactive shell where the message would disturb aliases are used instead (which in turn cannot be used in scripts).

GTK LookAndFeel

If your Java programs look ugly, you may want to set up the default look and feel for the swing components:

Some Java programs insist on using the cross platform Metal look and feel. In some of these cases you can force these applications to use the GTK look and feel by setting the following property:

GTK3 Support

In Java releases prior to version 9, the GTK LookAndFeel is linked against GTK2, whilst many newer desktop applications use GTK3. This incompatibility between GTK versions may break applications utilizing Java plugins with GUI, as the mixing of GTK2 and GTK3 in the same process is not supported (for example, LibreOffice 5.0).

The GTK LookAndFeel can be run against GTK versions 2, 2.2 and 3, defaulting to GTK3. This can be overridden by setting the following property:



Depending on the GUI framework, HiDPI#Java applications can be enabled using different methods.

Better 2D performance

Switching to OpenGL-based hardware acceleration pipeline will improve 2D performance

export JDK_JAVA_OPTIONS='-Dsun.java2d.opengl=true'
Note: Enabling this option may cause the UI of software like JetBrains IDEs misbehave, making them drawing windows, popups and toolbars partially.

See also