Replies: 3 comments 5 replies
|
Thanks for write-up. Since the EE editions are behind authentication these should be skipped. I don't want to support auth protected versions as downloading the actual binary also will require a login which would break in mise. The versioning is confusing though and does not align with the current So this would mean keeping the current versioning scheme of
|
|
Thank you to bring it back, those hundreds of lines are not trivial. However, there are some concerns that might be helped to know. Referencehttps://endoflife.date/oracle-graalvm We have official two sites, the graalvm.orgRelease Calender: https://www.graalvm.org/release-calendar/ docs.oracle.comRelease Calendar: https://docs.oracle.com/en/graalvm/release-calendar.html The OLD Release Calendar: https://docs.oracle.com/en/graalvm/jdk/20/docs/release-calendar First concernjdx/mise-java@132ea6f#diff-98cd46edf6b19b90a198e35cfbd40c162bdfe7f568348109f9f79bedf6c618e4R155 // Skip innovation releases (treated as early access)Just as a reminder, innovation and early release are different, we need to make sure to not conflating it. Oracle GraalVM's early access has its own GitHub releases page. And it is supposed to be released weekly according to the
Second concernThe
However, the
To sum up, we have two conventions here.
And those affect the URL scheme of some releases. Let's compare the old one against the newer one. {
"Files": {
"21.2.0.1-Windows-x86-8": {
"File": "https://download.oracle.com/otn/utilities_drivers/oracle-labs/graalvm-ee-java8-windows-amd64-21.2.0.1.zip"
},
"21.2.0.1-Windows-x86-11": {
"File": "https://download.oracle.com/otn/utilities_drivers/oracle-labs/graalvm-ee-java11-windows-amd64-21.2.0.1.zip"
},
"21.2.0.1-Windows-x86-16": {
"File": "https://download.oracle.com/otn/utilities_drivers/oracle-labs/graalvm-ee-java16-windows-amd64-21.2.0.1.zip"
}
}
}Notice we have the word of If we compare it with the new one: https://www.oracle.com/a/tech/docs/graalvm-23.1.12.json {
"Files": {
"23.1.12-Windows-x64-21": {
"File": "https://download.oracle.com/graalvm/21/archive/graalvm-jdk-21.0.12_windows-x64_bin.zip"
}
}
}
The old versioning remains in the download site and in the JSON key, however it was omitted in the file name. I know you decided to omit the enterprise one, but this discrepancy might be helpful to be documented. Third concernjdx/mise-java@6efdee2#diff-0bf37061220aa1b24ed12daa050b8f75af02eaeebb396e76faf753b954075b01R31792 {
"url": "https://download.oracle.com/otn/utilities_drivers/oracle-labs/graalvm-jdk-17.0.20_windows-x64_bin.zip"
}As far as I have observed, And if the URL contains |
|
Thanks again for the explanations. Addressed the 3rd concern since these URLs would not work in mise. |
|
Well done, good job. |
|
Crawler has been restored using the provided JSON URL but without adding any additional variants (such as Innovation or Enterprise) for now. Since Enterprise requires authentication these cannot be crawled and downloads would not work in mise. As for the Innovation releases its not quite clear if those could clash with JDK versions between Innovation 1 and Innovation 2. |
I've just read this: https://logicojp.medium.com/encountered-issues-when-using-the-graalvm-innovation-release-with-setup-graalvm-action-84781eb915cb Caution is needed to avoid conflating the GraalVM This is where things spiced up. I've observed that, while the versioning of modern GraalVM is using JEP 223, the modern JDK itself is using JEP 322 GraalVM, JDK,
If we take a look at the pattern: The I've looked it up, and there has been no cases where the So it's quite easy to set it up, once you understand it. |
|
Hmm, not only we need to comprehend the changes in GraalVM versioning but also the JDK versioning. To make it transparent, what if mise shows both of the JDK and GraalVM versioning clearly? That would require |
|
@roele Do you plan to add the innovation variant in the future? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Background
Related: #6831 and #6602
The crawler has existed, until it was removed in the commit of jdx/mise-java@d9d8245
And I do believe it's because of bad PR of the Oracle blog post.
Meanwhile, there's lot of discussion such as Reddit, Hacker news, Lobsters, or even the graal repo issue that signify the confusion.
Furthermore, there's also statements in the the archive download page.
Basically, Oracle decoupled GraalVM from the commercial Java SE ecosystem, treating it as a separate standalone product track, The development team's focus shifted to also support non-Java languages like GraalPy and GraalJS. Meanwhile, the standalone software remains accessible under the free GFTC license that Oracle introduced previously.
Therefore, the Oracle GraalVM release for Java is still continues.
Source to crawl
The official download site is this below.
https://www.oracle.com/downloads/graalvm-downloads.html [ Wayback link ]
From that site, with a browser's dev tools, we could find the main .json file that could be crawled.
https://www.oracle.com/a/tech/docs/graalvm-downloads.json [ Wayback link ]
Most importantly, it has a lot of keys named
JSON File, containing the .json files for the download links and the hashes.Furthermore, It also has the key of
TitleandSubTitlefor the context andJavaOSArchfor multiple JDK it's based on.In addition, the timestamp of the file could be obtained from the http response header of each file. For example,
curl --write-out "%header{last-modified}" --silent --location --range 0-0 --out-null https://gds.oracle.com/download/graal/25i2/archive/graalvm-jdk-25i2-25.0.4_windows-x64_bin.zipHowever, certain files (for example) require proper authentication to crawl properly, simply passing the
--cookieflag via curl is insufficient.For example, it might be required to remote debug a real browser and then hook it with playwright.
Consideration
oracle-graalvm-eetrack has been succeeded byoracle-graalvmandoracle-graalvm-innovationBut based on the support roadmap, some releases are still under extended support.
jdk#It might also helps to differentiate the fact that the GraalVM version number doesn't imply the JDK version it's based on, for example..jarinstaller file. Those were usually installed through the now discontinuedgutool bundled in the old release. So those will need to be prepackaged first for each arch, for example.But don't worry, the
.jarfile is easily extractable, for example with 7-zip, since it's essentially a.zipfile.mise latest java@oracle-graalvm-eemight returnsoracle-graalvm-ee-jdk17-22.3.5ororacle-graalvm-ee-jdk17-21.3.19depending on theversion_ordersetting.Summary
As per 2026-08-01, this table might summarized of what I proposed.
mise latestjava@oracle-graalvm-innovationoracle-graalvm-innovation-jdk25.0.4-25.2.4java@oracle-graalvmoracle-graalvm-jdk25.0.4-25.0.4java@oracle-graalvm-jdk25oracle-graalvm-jdk25.0.4-25.0.4java@oracle-graalvm-jdk21oracle-graalvm-jdk21.0.12-23.1.12java@oracle-graalvm-jdk17oracle-graalvm-jdk17.0.20-23.0.13java@oracle-graalvm-eeoracle-graalvm-ee-jdk17.0.10-22.3.5java@oracle-graalvm-ee-jdk17oracle-graalvm-ee-jdk17.0.10-22.3.5java@oracle-graalvm-ee-jdk11oracle-graalvm-ee-jdk11.0.22-22.3.5java@oracle-graalvm-ee-jdk8oracle-graalvm-ee-jdk8u501-21.3.19java@oracle-graalvm-ee-jdk17-21oracle-graalvm-ee-jdk17.0.20-21.3.19java@oracle-graalvm-ee-jdk11-21oracle-graalvm-ee-jdk11.0.32-21.3.19java@oracle-graalvm-ee-jdk8-21oracle-graalvm-ee-jdk8u501-21.3.19java@oracle-graalvm-ee-jdk16oracle-graalvm-ee-jdk16.0.2-21.2.0.1All reactions