For anyone getting a bunch of errors when they try to package the project

[IfeSunmola]

Change graalvm.version value in the ./pom.xml from 23.1.0 to 24.1.1

Truffle is built with GraalVM so a Graal JDK build is required. Anything less than JDK 21 will not work. If you're using sdk man, see https://sdkman.io/jdks#graalce OR https://sdkman.io/jdks#graal

I would have created a pull request for this but looks like pull requests are being ignored

[geomagilles]

Thanks @IfeSunmola!

[ahelwer]

For me (macOS aarch64, GraalVM 24.0.2+11.1 installed via graalvm-jdk homebrew package), mvn package fails because mvn test fails. mvn compile works. When running mvn test or mvn package I get a bunch of weird errors like:

SLSharedCodeSeparatedEnvTest.instrumentsSeeOutputOfBoth:148 Output of instrument goes not to os runtime if specified otherwise expected:<[]initializingOutputCa...> but was:<[[To redirect Truffle log output to a file use one of the following options:
* '--log.file=<path>' if the option is passed using a guest language launcher.
* '-Dpolyglot.log.file=<path>' if the option is passed using the host Java launcher.
* Configure logging using the polyglot embedding API.]
[engine] WARNING: The polyglot engine uses a fallback runtime that does not support runtime compilation to native code.
Execution without runtime compilation will negatively impact the guest application performance.
The following cause was found: JVMCI is not enabled for this JVM. Enable JVMCI using -XX:+EnableJVMCI.
For more information see: https://www.graalvm.org/latest/reference-manual/embed-languages/#runtime-optimization-support.
To disable this warning use the '--engine.WarnInterpreterOnly=false' option or the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
]initializingOutputCa...>

EDIT: I managed to fix this by setting my $JAVA_HOME environment variable to /opt/homebrew/Caskroom/graalvm-jdk/24.0.2,12/graalvm-jdk-24.0.2+11.1/Contents/Home/, or whatever your install directory is such that $JAVA_HOME/bin/java exists. Oddly the build system will detect & report an error if $JAVA_HOME is set to a nonexistent or incorrect directory, but it will not detect & report an error when $JAVA_HOME is not set at all.

I also recommend using sdkman instead of homebrew to manage your JDK installs on macOS, because homebrew really does not have a decent way of installing particular older versions.