{"id":15039249,"url":"https://github.com/adoptium/temurin-build","last_synced_at":"2025-10-06T21:24:36.387Z","repository":{"id":37096859,"uuid":"85294562","full_name":"adoptium/temurin-build","owner":"adoptium","description":"Eclipse Temurin™ build scripts - common across all releases/versions","archived":false,"fork":false,"pushed_at":"2025-05-12T22:55:19.000Z","size":7017,"stargazers_count":1059,"open_issues_count":283,"forks_count":265,"subscribers_count":60,"default_branch":"master","last_synced_at":"2025-05-12T23:34:16.650Z","etag":null,"topics":["cacert","docker-commands","docker-container","docker-group","hacktoberfest","shell-script","temurin"],"latest_commit_sha":null,"homepage":null,"language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/adoptium.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"security/.gitignore","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null},"funding":{"github":"adoptium","custom":["eclipse.org/donate/adoptium"]}},"created_at":"2017-03-17T09:31:50.000Z","updated_at":"2025-05-12T22:55:23.000Z","dependencies_parsed_at":"2024-01-10T00:26:34.915Z","dependency_job_id":"a87f0260-4b8e-4b53-aff5-ae2bcb9fcc67","html_url":"https://github.com/adoptium/temurin-build","commit_stats":{"total_commits":2324,"total_committers":114,"mean_commits":"20.385964912280702","dds":0.871342512908778,"last_synced_commit":"a53df222e22278c61e1b925eef19fc15cec43c8a"},"previous_names":["adoptopenjdk/openjdk-build"],"tags_count":10,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adoptium%2Ftemurin-build","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adoptium%2Ftemurin-build/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adoptium%2Ftemurin-build/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adoptium%2Ftemurin-build/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/adoptium","download_url":"https://codeload.github.com/adoptium/temurin-build/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254149976,"owners_count":22022852,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cacert","docker-commands","docker-container","docker-group","hacktoberfest","shell-script","temurin"],"created_at":"2024-09-24T20:42:05.551Z","updated_at":"2025-10-06T21:24:36.366Z","avatar_url":"https://github.com/adoptium.png","language":"Shell","funding_links":["https://github.com/sponsors/adoptium","eclipse.org/donate/adoptium"],"categories":["JDK","Shell"],"sub_categories":[],"readme":"\u003c!-- textlint-disable terminology --\u003e\n# Repository for code and instructions for building OpenJDK binaries, defaulting to Eclipse Temurin™\n\nThese scripts can be used to build OpenJDK anywhere but are primarily used by Eclipse Adoptium members (vendors) to build binaries. The scripts default to the use case of building Eclipse Temurin binaries which occurs on the build farm at \u003chttps://ci.adoptium.net\u003e. Those binaries are then made available for consumption at \u003chttps://adoptium.net\u003e and via the API \u003chttps://api.adoptium.net\u003e.\n\n**NOTE** In the future, adoptium.net will transition to being a marketplace for other qualifying vendors as well Eclipse Temurin.\n\n## Where can I find the release status of Eclipse Temurin™ binaries?\n\nGo to the [Eclipse Adoptium Top Level Project repository](https://www.github.com/adoptium/adoptium/issues) for release tracking.\n\n## TL;DR: I want to build a JDK NOW\n\n### Build jdk natively on your system\n\nTo do this you will need to have your machine set up with a suitable\ncompiler and various other tools available. We set up our machines using\nansible playbooks from the [openjdk-infrastructure](https://github.com/adoptopenjdk/openjdk-infrastructure) repository.\nYou can also look at the [dockerfile generator](https://github.com/adoptium/temurin-build/blob/master/docker/dockerfile-generator.sh) for a list of required packages for Ubuntu.\n\nOnce you've got all of the prerequisites installed, clone this openjdk-build\nrepository (`git clone https://github.com/adoptium/temurin-build` and\nkick off a build a follows with this script. The `-J` parameter specifies\nthe \"boot JDK\" which should generally be one major version prior to the one\nyou are building (although one of the same major version will also work).\nNote that the build variant defaults to HotSpot if omitted which builds from the same repositories as Temurin.\n\nIf you're using wsl, use the `--wsl` flag (ie: `./makejdk-any-platform.sh -J /usr/lib/jvm/java-21-openjdk-amd64 --wsl --create-sbom jdk21`).\n\n```bash\n./makejdk-any-platform.sh (-J /usr/lib/jvm/jdk-xx) (--build-variant \u003chotspot|openj9|corretto|SapMachine|dragonwell|bisheng\u003e) \u003cjdk8u|jdk11u|jdk16u|jdk\u003e\n```\n\ne.g.\n\n```bash\n./makejdk-any-platform.sh -J /usr/lib/jvm/jdk-10.0.2 --build-variant hotspot jdk11u\n```\n\n## How do I build OpenJDK in a docker image?\n\nIf you do not want to set up your machine with all the prerequisites for\nbuilding OpenJDK, you can use our docker images under the [docker]\ndirectory as follows (first version builds HotSpot, second builds J9 - the\nfinal parameter can be adjusted to build whichever version you want as long\nas we can generate valid dockerfile for it):\n\n```bash\n./makejdk-any-platform.sh --docker --clean-docker-build jdk8u\n./makejdk-any-platform.sh --podman --clean-docker-build --build-variant openj9 jdk11u\n```\n\nWe test these dockerfiles on a regular basis in the\n[Dockerfilecheck](https://ci.adoptium.net/job/DockerfileCheck/) job\nto ensure they continue to work in a stable fashion.\n\n## Repository contents\n\nThis repository contains several useful scripts in order to build OpenJDK\npersonally or at build farm scale.\n\n1. The `build-farm` folder contains shell scripts for multi configuration Jenkins\nbuild jobs used for building Adoptium OpenJDK binaries.\n1. The `docker` folder contains tools for generating dockerfiles which can be used as part of building\nOpenJDK inside a Docker container.\n1. The `git-hg` folder has now been moved to it's own separate repository. See [openjdk-mirror-scripts](https://github.com/adoptium/mirror-scripts).\n1. The `pipelines` folder has now been moved to a separate repo: \u003chttps://github.com/adoptium/ci-jenkins-pipelines\u003e.\n1. The `sbin` folder contains the scripts that actually build (Temurin).\n`build.sh` is the entry point which can be used stand alone but is typically\ncalled by the `native-build.sh` or `docker-build.sh` scripts (which themselves\nare typically called by `makejdk-any-platform.sh`).\n1. The `security` folder contains a script and `cacerts` file that is bundled\nwith the JDK and used when building OpenJDK: the `cacerts` file is an important\nfile that's used to enable SSL connections.\n\n## The makejdk-any-platform.sh script\n\n`makejdk-any-platform.sh` is the entry point for building (Adoptium) OpenJDK binaries.\nBuilding natively or in a docker container are both supported. This script (and\nits supporting scripts) have defaults, but you can override these as needed.\nThe scripts will auto detect the platform and architecture it is running on and\nconfigure the OpenJDK build accordingly.  The supporting scripts will also\ndownload and locally install any required dependencies for the OpenJDK build,\ne.g. The ALSA sound and Freetype font libraries.\n\nMany of the configuration options are passed through to the `configure` and\n`make` commands that OpenJDK uses to build binaries.  Please see the appropriate\n_README-builds.html_ file for the OpenJDK source repository that you are building.\n\n**NOTE:** Usage can be found via `makejdk-any-platform.sh --help`. Here is the\nman page re-formatted for convenience.\n\n```bash\nUSAGE\n\n./makejdk-any-platform [options] version\n\nPlease visit https://www.adoptium.net for further support.\n\nVERSIONS\n\njdk8u - Build Java 8, defaults to https://github.com/adoptium/jdk8u\njdk11u - Build Java 11, defaults to https://github.com/adoptium/jdk11u\njdk16u - Build Java 16, defaults to https://github.com/adoptium/jdk16u\njdk - Build Latest Java (Alpha/Beta), defaults to https://github.com/adoptium/jdk\n\nOPTIONS\n\n-b, --branch \u003cbranch\u003e\nspecify a custom branch to build from, e.g. dev.\nFor reference, Adoptium GitHub source repositories default to the dev\nbranch which may contain a very small diff set to the master branch\n(which is a clone from the OpenJDK mercurial forest).\n\n-B, --build-number \u003cbuild_number\u003e\nspecify the OpenJDK build number to build from, e.g. b12.\nFor reference, OpenJDK version numbers look like 1.8.0_162-b12 (for Java 8) or\n9.0.4+11 (for Java 9+) with the build number being the suffix at the end.\n\n--build-variant \u003cvariant_name\u003e\nspecify a OpenJDK build variant, e.g. openj9.\nFor reference, the default variant is hotspot and does not need to be specified.\n\n-c, --clean-docker-build\nremoves the existing docker container and persistent volume before starting\na new docker based build.\n\n-C, --configure-args \u003cargs\u003e\nspecify any custom user configuration arguments, using\ntemporary_speech_mark_placeholder in the place of any speech marks.\n\n--clean-git-repo\nclean out any 'bad' local git repository you already have.\n\n--create-debug-image\ncreate a debug-image archive with the debug symbols.\n\n--create-jre-image\ncreate the legacy JRE image in addition to the JDK image.\n\n--create-sbom\ncreate the CycloneDX System Bill of Materials (JSON artifact).\n\n-d, --destination \u003cpath\u003e\nspecify the location for the built binary, e.g. /path/.\nThis is typically used in conjunction with -T to create a custom path\n/ file name for the resulting binary.\n\n-D, --docker, --podman\nbuild OpenJDK in a docker/podman container. -D will autodetect, using podman if found, docker otherwise.\n\n--cross-compile\nuse this if you are cross compiling - it will skip the java -version checks at the end\n\n--debug-docker\ndebug OpenJDK build script in a docker container. Only valid if -D is selected.\n\n--disable-shallow-git-clone\ndisable the default fB--depth=1 shallow cloning of git repo(s).\n\n-f, --freetype-dir\nspecify the location of an existing FreeType library.\nThis is typically used in conjunction with -F.\n\n--freetype-build-param \u003cparameter\u003e\nspecify any special freetype build parameters (required for some Operating Systems).\n\n--freetype-version \u003cversion\u003e\nspecify the version of freetype you are building.\n\n-F, --skip-freetype\nskip building Freetype automatically.\nThis is typically used in conjunction with -f.\n\n-h, --help\nprint the man page.\n\n-i, --ignore-container\nignore the existing docker container if you have one already.\n\n-J, --jdk-boot-dir \u003cjdk_boot_dir\u003e\nspecify the JDK boot dir.\nFor reference, OpenJDK needs the previous version of a JDK in order to build\nitself. You should select the path to a JDK install that is N-1 versions below\nthe one you are trying to build.\n\n-k, --keep\nif using docker, keep the container after the build.\n\n--local-dependency-cache-dir \u003cLocal dependency cache directory\u003e\nspecify the location of a local cache of required build dependency jars. If not specified\nthe following default locations are searched\nWindows: c:/dependency_cache\nMacOS: ${HOME}/dependency_cache\nUnix: /usr/local/dependency_cache\n\n--make-exploded-image\ncreates an exploded image (useful for codesigning jmods). Use --assemble-exploded-image once you have signed the jmods to complete the packaging steps.\n\n--custom-cacerts \u003ctrue|false\u003e\nIf true (default), a custom cacerts file will be generated based on the Mozilla list of CA certificates (see folder security/). If false, the file shipped by OpenJDK will be used.\n\n-n, --no-colour\ndisable colour output.\n\n-p, --processors \u003cargs\u003e\nspecify the number of processors to use for the docker build.\n\n-r, --repository \u003crepository\u003e\nspecify the repository to clone OpenJDK source from,\ne.g. https://github.com/karianna/openjdk-jdk8u.\n\n-s, --source \u003cpath\u003e\nspecify the location to clone the OpenJDK source (and dependencies) to.\n\n-S, --ssh\nuse ssh when cloning git.\nIn case of docker build add github.com to ~/.ssh/known_hosts (e.g.: ssh github.com)\nif your ssh key has a passphrase, add it to ssh-agent (e.g.: ssh-add ~/.ssh/id_rsa)\n\n--sign\nsign the OpenJDK binary that you build.\n\n--sudo\nrun the docker container as root.\n\n-t, --tag \u003ctag\u003e\nspecify the repository tag that you want to build OpenJDK from.\n\n-T, --target-file-name \u003cfile_name\u003e\nspecify the final name of the OpenJDK binary.\nThis is typically used in conjunction with -D to create a custom file\nname for the resulting binary.\n\n--tmp-space-build\nuse the temp directory for performing the build\n\n-u, --update-version \u003cupdate_version\u003e\nspecify the update version to build OpenJDK from, e.g. 162.\nFor reference, OpenJDK version numbers look like 1.8.0_162-b12 (for Java 8) or\n9.0.4+11 (for Java 9+) with the update number being the number after the '_'\n(162) or the 3rd position in the semVer version string (4).\nThis is typically used in conjunction with -b.\n\n--use-adoptium-devkit \u003cAdoptium DevKit release tag\u003e\nDownload and use the given DevKit from https://github.com/adoptium/devkit-binaries/releases.\nThe DevKit is downloaded and unpacked to WORKSPACE_DIR/WORKING_DIR/devkit\nand will add the configure arg --with-devkit=WORKSPACE_DIR/WORKING_DIR/devkit.\n\n--use-jep319-certs\nUse certs defined in JEP319 in Java 8/9. Deprecated, has no effect.\n\n--user-openjdk-build-root-directory \u003copenjdk build root path\u003e\nUse a user specified openjdk build root directory, rather than the OpenJDK git source directory.\nThe directory must be empty, or not exist (in which case it gets created).\n\n-v, --version\nspecify the OpenJDK version to build e.g. jdk8u.  Left for backwards compatibility.\n\n-V, --jvm-variant \u003cjvm_variant\u003e\nspecify the JVM variant (server or client), defaults to server.\n\nExample usage:\n\n./makejdk-any-platform -D jdk8u\n./makejdk-any-platform -T MyOpenJDK10.tar.gz jdk10\n\n```\n\n### Script Relationships\n\n![Build Variant Workflow](https://github.com/adoptium/ci-jenkins-pipelines/blob/master/docs/images/AdoptOpenJDK_Build_Script_Relationships.png)\n\nThe main script to build OpenJDK is `makejdk-any-platform.sh`, which itself uses\nand/or calls `configureBuild.sh`, `docker-build.sh` and/or `native-build.sh`.\n\nThe structure of a build is:\n\n 1. Configuration phase determines what the configuration of the build is based on your current\nplatform and and optional arguments provided\n 1. Configuration is written out to `config/built_config.cfg`\n 1. Build is kicked off by either creating a docker container or running the native build script\n 1. Build reads in configuration from `built_config.cfg`\n 1. Downloads source, dependencies and prepares build workspace\n 1. Invoke OpenJDK build via `make`\n 1. Package up built artifacts\n\n- Configuration phase is primarily performed by [configureBuild.sh](https://github.com/adoptium/temurin-build/blob/master/configureBuild.sh) and [makejdk-any-platform.sh](https://github.com/adoptium/temurin-build/blob/master/makejdk-any-platform.sh).\n- If a docker container is required it is built by [docker-build.sh](https://github.com/adoptium/temurin-build/blob/master/docker-build.sh) otherwise [native-build.sh](https://github.com/adoptium/temurin-build/blob/master/native-build.sh).\n- In the build phase [sbin/build.sh](https://github.com/adoptium/temurin-build/blob/master/sbin/build.sh) is invoked either natively or inside the docker container.\n`sbin/build.sh` invokes [sbin/prepareWorkspace.sh](https://github.com/adoptium/temurin-build/blob/master/sbin/prepareWorkspace.sh) to download dependencies, source and perform\ngeneral preparation.\n- Rest of the build and packaging is then handled from `sbin/build.sh`\n\n## Building OpenJDK from other locations\n\n### Building OpenJDK from a non-Adoptium repository\n\nThese scripts default to using Adoptium as the OpenJDK source repository to build\nfrom, but you can override this with the `-r` flag. If you want to run from a\nnon-default branch you can also specify -b e.g.\n\n```bash\n./makejdk-any-platform.sh -r https://github.com/sxa/openjdk-jdk8u -b main -J /usr/lib/jvm/java-1.7.0 jdk8u\n```\n\n### Building in a custom directory\n\nExample Usage\n\n```bash\n./makejdk-any-platform.sh -J /usr/lib/jvm/jdk-10.0.2 -s $HOME/openjdk-jdk11u/src -d $HOME/openjdk-jdk11u/build -T MyOpenJDK11.tar.gz jdk11u\n```\n\nThis would clone OpenJDK source from \u003chttps://github.com/adoptium/openjdk-jdk11u\u003e\nto `$HOME/openjdk-jdk11u/src`, configure the build with sensible defaults according\nto your local platform and then build OpenJDK and place the result in\n`/home/openjdk/target/MyOpenJDK11.tar.gz`.\n\n## Metadata\n\nAlongside the built assets a metadata file will be created with info about the build. This will be a JSON document of the form:\n\n```json\n{\n    \"vendor\": \"Eclipse Adoptium\",\n    \"os\": \"mac\",\n    \"arch\": \"x64\",\n    \"variant\": \"openj9\",\n    \"variant_version\": {\n        \"major\": \"0\",\n        \"minor\": \"22\",\n        \"security\": \"0\",\n        \"tags\": \"m2\"\n    },\n    \"version\": {\n        \"minor\": 0,\n        \"security\": 0,\n        \"pre\": null,\n        \"adopt_build_number\": 0,\n        \"major\": 15,\n        \"version\": \"15+29-202007070926\",\n        \"semver\": \"15.0.0+29.0.202007070926\",\n        \"build\": 29,\n        \"opt\": \"202007070926\"\n    },\n    \"scmRef\": \"\u003coutput of git describe OR buildConfig.SCM_REF\u003e\",\n    \"buildRef\": \"\u003cbuild-repo-name/build-commit-sha\u003e\",\n    \"version_data\": \"jdk15\",\n    \"binary_type\": \"debugimage\",\n    \"sha256\": \"\u003cshasum\u003e\",\n    \"full_version_output\": \"\u003coutput of java --version\u003e\",\n    \"configure_arguments\": \"\u003coutput of bash configure\u003e\"\n}\n```\n\nThe Metadata class is contained in the [Metadata.groovy](https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/library/src/common/MetaData.groovy) file and the Json is constructed and written in the [openjdk_build_pipeline.groovy](https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/build/common/openjdk_build_pipeline.groovy) file.\n\nIt is worth noting the additional tags on the SemVer is the build number.\n\nBelow are all of the keys contained in the metadata file and some example values that can be present.\n\n----\n\n- `vendor:`\nExample values: [`Eclipse Adoptium`, `Alibaba`]\n\nThis tag is used to identify the vendor of the JDK being built, this value is set in the [build.sh](https://github.com/adoptium/temurin-build/blob/805e76acbb8a994abc1fb4b7d582486d48117ee8/sbin/build.sh#L183) file and defaults to \"Adoptium\".\n\n----\n\n- `os:`\nExample values: [`windows`, `mac`, `linux`, `aix`, `solaris`]\n\nThis tag identifies the operating system the JDK has been built on (and should be used on).\n\n----\n\n- `arch:`\nExample values: [`aarch64`, `ppc64`, `s390x`, `x64`, `x86-32`, `arm`]\n\nThis tag identifies the architecture the JDK has been built on and it intended to run on.\n\n----\n\n- `variant:`\nExample values: [`hotspot`, `openj9`, `corretto`, `dragonwell`, `bisheng`]\n\nThis tag identifies the JVM being used by the JDK. \"dragonwell\" and \"bisheng\" itself are HotSpot based JVMs but are currently considered their own variants for the purposes of build.\nWARN: This will be changed at a later date when we split out JVM from vendor.\n\n----\n\n- `variant_version:`\n\nThis tag is used to identify a version number of the variant being built, it currently is exclusively used by OpenJ9 and has the following keys:\n\n- `major:`\nExample values: [`0`, `1`]\n\n- `minor:`\nExample values: [`22`, `23`, `24`]\n\n- `security:`\nExample values: [`0`, `1`]\n\n- `tags:`\nExample values: [`m1`, `m2`]\n\n----\n\n- `version:`\n\nThis tag contains the full version information of the JDK built, it uses the [VersionInfo.groovy](https://github.com/adoptium/temurin-build/blob/master/pipelines/library/src/common/VersionInfo.groovy) class and the [ParseVersion.groovy](https://github.com/adoptium/temurin-build/blob/master/pipelines/library/src/ParseVersion.groovy) class.\n\nIt contains the following keys:\n\n- `minor:`\nExample values: [`0`]\n\n- `security:`\nExample Values: [`0`, `9`, `252` `272`]\n\n- `pre:`\nExample values: [`null`]\n\n- `adopt_build_number:`\nExample values: [`0`]\nIf the `ADOPT_BUILD_NUMBER` parameter is used to build te JDK that value will appear here, otherwise a default value of 0 appears.\n\n- `major:`\nExample values: [`8`, `11`, `15`, `16`]\n\n- `version:`\nExample values: [`1.8.0_272-202010111709-b09`, `11.0.9+10-202010122348`, `14.0.2+11-202007272039`, `16+19-202010120348`]\n\n- `semver:`\nExample values: [`8.0.202+8.0.202008210941`, `11.0.9+10.0.202010122348`, `14.0.2+11.0.202007272039`, `16.0.0+19.0.202010120339`]\nFormed from the major, minor, security, and build number by the [formSemver()](https://github.com/adoptium/temurin-build/blob/805e76acbb8a994abc1fb4b7d582486d48117ee8/pipelines/library/src/common/VersionInfo.groovy#L123) function.\n\n- `build:`\nExample values: [`6`, `9`, `18`]\nThe OpenJDK build number for the JDK being built.\n\n- `opt:`\nExample values: [`202008210941`, `202010120348`, `202007272039`]\n\n----\n\n- `scmRef:`\nExample values: [`dragonwell-8.4.4_jdk8u262-b10`, `jdk-16+19_adopt-61198-g59e3baa94ac`, `jdk-11.0.9+10_adopt-197-g11f44f68c5`, `23f997ca1`]\n\nA reference the the base JDK repository being build, usually including a GitHub commit reference, i.e. `jdk-16+19_adopt-61198-g59e3baa94ac` links to `https://github.com/adoptium/openjdk-jdk/commit/59e3baa94ac` via the commit SHA **59e3baa94ac**.\n\nValues that only contain a commit reference such as `23f997ca1` are OpenJ9 commits on their respective JDK repositories, for example **23f997ca1** links to the commit `https://github.com/ibmruntimes/openj9-openjdk-jdk14/commit/23f997ca1.`\n\n----\n\n- `buildRef:`\nExample values: [`openjdk-build/fe0f2dba`, `openjdk-build/f412a523`]\nA reference to the build tools repository used to create the JDK, uses the format **repository-name**/**commit-SHA**.\n\n----\n\n- `version_data:`\nExample values: [`jdk8u`, `jdk11u`, `jdk14u`, `jdk`]\n\n----\n\n- `binary_type:`\nExample values: [`jdk`, `jre`, `debugimage`, `testimage`]\n\n----\n\n- `sha256:`\nExample values: [`20278aa9459e7636f6237e85fcd68deec1f42fa90c6c541a2dfa127f4156d3e2`, `2f9700bd75a807614d6d525fbd8d016c609a9ea71bf1ffd5d4839f3c1c8e4b8e`]\nA SHA to verify the contents of the JDK.\n\n----\n\n- `full_version_output:`\nExample values:\n\n```java\nopenjdk version \\\"1.8.0_252\\\"\\nOpenJDK Runtime Environment (Alibaba Dragonwell 8.4.4) (build 1.8.0_252-202010111720-b06)\\nOpenJDK 64-Bit Server VM (Alibaba Dragonwell 8.4.4) (build 25.252-b06, mixed mode)\\n`\n```\n\nThe full output of the command `java -version` for the JDK.\n\n----\n\n- `configure_arguments:`\nThe full output generated by `configure.sh` for the JDK built.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fadoptium%2Ftemurin-build","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fadoptium%2Ftemurin-build","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fadoptium%2Ftemurin-build/lists"}