Currently, when Elasticsearch bundles a JDK with a release it comes from the Oracle’s website or from a selfhosted Artifactory server hosted by Elastic depending on the bundled_jdk configs in version.properties.
Not sure the design decision behind using Artifactory but AdoptOpenJDK now provides an official API to retrieve downloads.
When picking AdoptOpenJDK as a vendor, Elasticsearch should use the API to retrieve JDKs from the official AdoptOpenJDK source.
Here are the advantages:
-
Unifying the process to download JDKs. Both, AdoptOpenJDK and Oracle, will now pull from their respective official download sources
-
People will not have to trust “random” binaries on Elastic’s Artifactory server
-
Elastic no longer needs to maintain an external antifactory for JDKs
Currently, when Elasticsearch bundles a JDK with a release it comes from the Oracle’s website or from a selfhosted Artifactory server hosted by Elastic depending on the
bundled_jdkconfigs inversion.properties.Not sure the design decision behind using Artifactory but AdoptOpenJDK now provides an official API to retrieve downloads.
When picking
AdoptOpenJDKas a vendor, Elasticsearch should use the API to retrieve JDKs from the official AdoptOpenJDK source.Here are the advantages:
Unifying the process to download JDKs. Both, AdoptOpenJDK and Oracle, will now pull from their respective official download sources
People will not have to trust “random” binaries on Elastic’s Artifactory server
Elastic no longer needs to maintain an external antifactory for JDKs