Package Details: jdk19-graalvm-bin 22.3.1-1

Git Clone URL: (read-only, click to copy)
Package Base: jdk19-graalvm-bin
Description: Universal virtual machine for running applications written in a variety of languages (JVM-based, LLVM-based, or other), Java 19 version
Upstream URL:
Licenses: custom
Provides: java-environment, java-runtime
Submitter: lucaswerkmeister
Maintainer: lucaswerkmeister
Last Packager: lucaswerkmeister
Votes: 5
Popularity: 0.002579
First Submitted: 2022-10-25 20:42 (UTC)
Last Updated: 2023-01-26 22:03 (UTC)

Required by (2444)

Sources (3)

Latest Comments

lucaswerkmeister commented on 2023-06-17 13:44 (UTC)

JDK 19 is no longer supported – all users of this package should instead install either jdk20-graalvm-bin (latest) or jdk17-graalvm-bin (LTS).

NextWorks commented on 2023-01-17 07:30 (UTC)

@lucaswerkmeister Didn't know about that because i use jdk19-graal as default. Thanks for the reply

lucaswerkmeister commented on 2023-01-17 00:57 (UTC) (edited on 2023-01-17 00:57 (UTC) by lucaswerkmeister)

@NextWorks: No, that’s not how JDK/JRE packages should work on Arch Linux. (See e.g. the jdk-openjdk file list at, which doesn’t touch /etc/profile.d either.) Instead, users can install multiple Java versions and use the archlinux-java command to select the default one, e.g. sudo archlinux-java set java-19-graalvm.

This package includes an install script which is supposed to call archlinux-java automatically if no default JDK has been configured yet, or to print a notice like this if it already has been set (but the notice is only shown on install, not on upgrade):

Default Java environment is already set to 'java-19-openjdk'
See 'archlinux-java help' to change it

However, due to a copy+paste mistake on my part, the install script was broken (I forgot to change 17 to 19 in it). I’ve fixed that now – if you upgrade the package, it should automatically set itself as the default Java on your system (assuming you don’t already have another Java installed).

NextWorks commented on 2023-01-16 22:23 (UTC) (edited on 2023-01-16 22:23 (UTC) by NextWorks)

Hello, i think you can put these two functions at the end of the pkgbuild

echo 'export PATH="/usr/lib/jvm/java-'$java_'-graalvm/bin:$PATH"' >> $pkgdir/etc/profile.d/

echo 'export JAVA_HOME="/usr/lib/jvm/java-'$java_'-graalvm"' >> $pkgdir/etc/profile.d/

The first function, "export PATH=/path/to/<graalvm>/bin:$PATH" adds the path of the GraalVM binary to the PATH environment variable. This allows the system to search for and execute commands from that specific location. The second function, "export JAVA_HOME=/path/to/<graalvm>" sets the JAVA_HOME environment variable to the path of the GraalVM installation. This allows other applications to know where the Java runtime environment is located.

Best Regards, NextWorks