You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 22, 2024. It is now read-only.
I thought I'd got my build working with JDK17 following your example (using Zulu on Windows), but when I run in GitHub Actions (Zulu on Ubuntu) Surefire bombs out with the message: Cannot use JVMCI compiler: No JVMCI compiler found.
It is unclear what the implications of removing JVMCI are for polyglot programming on OpenJDK.
The text was updated successfully, but these errors were encountered:
Oh, actually I think I might have just resolved my issue.
In the pom you have:
--upgrade-module-path=${compiler.dir}/compiler.jar:${compiler.dir}/compiler-management.jar
To work on Windows that needs a semicolon:
--upgrade-module-path=${compiler.dir}/compiler.jar;${compiler.dir}/compiler-management.jar
The docs (https://docs.oracle.com/en/java/javase/17/docs/specs/man/java.html) are quite specific that is should be a semicolon, but that definitely doesn't work on Linux.
Fortunately the docs also state that it's a list of directories, so this seems to work:
--upgrade-module-path=${compiler.dir}
I thought I'd got my build working with JDK17 following your example (using Zulu on Windows), but when I run in GitHub Actions (Zulu on Ubuntu) Surefire bombs out with the message: Cannot use JVMCI compiler: No JVMCI compiler found.
It is unclear what the implications of removing JVMCI are for polyglot programming on OpenJDK.
The text was updated successfully, but these errors were encountered: