GraalVM Community Edition #742
Labels
feature request
New feature or request to improve the current logic
Comments
msgilligan
added
feature request
msgilligan
added a commit
to msgilligan/bitcoinj
that referenced
this issue
Feb 1, 2025
We can now use the same setup_java GitHub Action in gradle.yml and graalvm.yml. This commit switches to the setup_java action from the setup-graalvm action and also changes some variable names to more closely match gradle.yml. The setup_java Action at this time only supports _Oracle_ GraalVM which is licensed under the GFTC license: https://www.oracle.com/downloads/licenses/graal-free-license.html See: actions/setup-java#742 So the benefits of using the same action for JDK and GraalVM have to be weighed against using only a non-FOSS version of GraalVM. Oracle GraalVM has stopped providing updates under the free-beer license for JDK 17, so I removed `17` from the matrix. It is also possible to use the last version: `17.0.12` The setup_graalvm action supports the Community Edition, Oracle GraalVM, and some other options. (It might even be possible/desirable to combine the two workflows in the future, but let's keep this PR simple)
|
Hi @msgilligan, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The GraalVM Community edition should be an option. It is nice to use the
setup_javaaction for matrix builds and consistency between regular JDK and GraalVM workflows. But it would be nice to be able to use the Community Edition in addition to the Oracle (non-FOSS) version.The text was updated successfully, but these errors were encountered: