René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow differentiating Zulu releases with/without CRaC","articleBody":"**Description:**\r\n\r\nCurrently, if I specify the following options:\r\n\r\n```yaml\r\ndistribution: 'zulu'\r\njava-version: '21'\r\n```\r\n\r\nThen `actions/setup-java` will download `zulu21.34.19-ca-crac-jdk21.0.3-linux_x64.tar.gz`. Notice that this is the build with the optional CRaC feature (`-crac` in the name) rather than the default build (`zulu21.34.19-ca-jdk21.0.3-linux_x64.tar.gz`). Not necessarily a big deal, but weird since this is an optional feature rather than the default Zulu build. This doesn't seem intentional, rather it just happens because the `-crac` version ends up being first in the list.\r\n\r\nI investigated a bit, and setup-java uses the `https://api.azul.com/zulu/download/community/v1.0/bundles/` API, which does not seem to offer the ability to filter out CRaC builds. Azul recommends migrating to the newer `https://api.azul.com/metadata/v1/zulu/packages/` API (see [the migration guide](https://docs.azul.com/core/metadata-api-migration)), which does have such a filter.\r\n\r\nAfter a few tests with the [Swagger UI for the new API](https://api.azul.com/metadata/v1/docs/swagger), here's the queries I would probably expect (assuming Linux x64 and `java-version: '21'` for this example):\r\n\r\n- `java-package: 'jdk'` (or the default): `https://api.azul.com/metadata/v1/zulu/packages/?java_version=21\u0026os=linux-glibc\u0026arch=x64\u0026archive_type=tar.gz\u0026java_package_type=jdk\u0026latest=true\u0026release_status=ga\u0026availability_types=ca\u0026certifications=tck\u0026javafx_bundled=false\u0026crac_supported=false`\r\n- `java-package: 'jdk+fx'`: `https://api.azul.com/metadata/v1/zulu/packages/?java_version=21\u0026os=linux-glibc\u0026arch=x64\u0026archive_type=tar.gz\u0026java_package_type=jdk\u0026latest=true\u0026release_status=ga\u0026availability_types=ca\u0026certifications=tck\u0026javafx_bundled=true\u0026crac_supported=false`\r\n- `java-package: 'jdk+crac'`: `https://api.azul.com/metadata/v1/zulu/packages/?java_version=21\u0026os=linux-glibc\u0026arch=x64\u0026archive_type=tar.gz\u0026java_package_type=jdk\u0026latest=true\u0026release_status=ga\u0026availability_types=ca\u0026certifications=tck\u0026javafx_bundled=false\u0026crac_supported=true`\r\n- Azul doesn't seem to offer packages with both JavaFX and CRaC at the same time.\r\n\r\nWhat do you think?\r\n\r\n**Justification:**\r\n\r\n- The optional inclusion of CRaC should be treated like the optional bundling of JavaFX (i.e. an option but not the default).\r\n- AFAICT, this requires migrating to Azul's new API, but that's what they recommend anyway.\r\n\r\nNote that I don't know of any specific issue with using the `-crac` build when it's not needed, so it would be more for the principle of intentionally selecting the type of build used rather than just getting whichever one happens to be first in the list.\r\n\r\n**Are you willing to submit a PR?**\r\n\r\nI can probably try, it doesn't seem too complicated - but no guarantee that I would have the time right away.","author":{"url":"https://github.com/guilgaly","@type":"Person","name":"guilgaly"},"datePublished":"2024-06-04T14:08:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/636/setup-java/issues/636"}