We will modify the Oracle Buildpack to include support for the new Oracle GraalVM distribution.
In addition, the existing graalvm
buildpack will be clarified to indicate that it is the GraalVM Community buildpack. We cannot change its ID, but we will update the README and metadata to clarify this point.
There are multiple motivations for this RFC:
- Oracle has introduced Oracle GraalVM, a new and free GraalVM distribution that provides advanced features including G1 GC, SBOM, as well as performance and size optimizations. A new buildpack for Oracle GraalVM will, for example, allow Spring users to build more efficient and secure microservices.
- The
graalvm
buildpack only supports GraalVM Community Edition. Since this is only one of many GraalVM distributions (Community Edition, Oracle GraalVM, Liberica NIK, Mandrel, ...), it makes sense to adjust the name and the README of the buildpack, so that it is clear to users which distribution the buildpack includes (Community Edition). - The latest GraalVM release has dropped the GraalVM version in favor of the Java version, which may simplify the implementation and maintenance of the buildpack.
- Due to the alignment with OpenJDK, GraalVM is becoming more and more a standard JDK with Native Image support. The GraalVM Updater will be deprecated in the GraalVM for JDK 21 release and removed in the future.
This RFC proposes to address the items listed under Motivation as follows:
- Update the Oracle Buildpack to support Oracle GraalVM. This will work just like what we have with the present Bellsoft Liberica buildpack, where the buildpack can provide a JVM and Native image tools.
- Update the README & buildpack metadata for the existing GraalVM buildpack to indicate it is specifically for the GraalVM Community release.
For more details, please see the proof of concept.
Alternatively, the existing graalvm
buildpack could be reworked and extended with support for Oracle GraalVM. For this, we would need to offer an environment variable such as $BP_DISTRIBUTION
for users to select a specific GraalVM distribution. However, that would be somewhat inconsistent with the bellsoft-liberica
buildpack, which also includes a GraalVM distribution. Having separate buildpacks for different GraalVM distributions is also more consistent with the Java buildpacks.
See the Details section. The implementation plan as well as a proof of concept PR are documented there.