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
Builds of GraalVM contain, like many JDK builds, a release file with information about the build, Java version etc. The release files for other JDKs, like Zulu or Oracle or Temurin builds of OpenJDK, can be evaluated directly as a set of environment variables, making it easy to load these values into a launcher script. However GraalVM builds include an additional COMMIT_INFO line that is not quoted and cannot be evaluated by a script.
Other than this COMMIT_INFO line, all elements are named and quoted correctly to act as environment variables. The formatting of COMMIT_INFO (which appears to be json) breaks that usage.
Matching other JDKs and avoiding the inclusion of unquoted, complex structured data would allow GraalVM to work better with consumers of the release file.
See jruby/jruby#8747 for an example of the sort of problem this introduces.
The text was updated successfully, but these errors were encountered:
We are looking into removing the COMMIT_INFO field from our release file. There's a couple of internal usages that we need to patch, but this should not be a blocker.
However, AFAIK, we do not explicitly support to "shell-evaluate" or "source" the release file.
@headius would it be ok with you to rename this issue to something limited to the inconsistent quotation of COMMIT_INFO?
I know there's not really any standard around the release file, but this seemed far enough out of the norm to report. We will have to work around it for earlier releases but we appreciate the fix. I think it's a good idea to keep this file simple going forward.
Builds of GraalVM contain, like many JDK builds, a
release
file with information about the build, Java version etc. The release files for other JDKs, like Zulu or Oracle or Temurin builds of OpenJDK, can be evaluated directly as a set of environment variables, making it easy to load these values into a launcher script. However GraalVM builds include an additionalCOMMIT_INFO
line that is not quoted and cannot be evaluated by a script.Here's the
release
file from my recent download:Other than this
COMMIT_INFO
line, all elements are named and quoted correctly to act as environment variables. The formatting ofCOMMIT_INFO
(which appears to be json) breaks that usage.Matching other JDKs and avoiding the inclusion of unquoted, complex structured data would allow GraalVM to work better with consumers of the
release
file.See jruby/jruby#8747 for an example of the sort of problem this introduces.
The text was updated successfully, but these errors were encountered: