Skip to content

Documentation on how to add and support new java versions to graalvm #12194

@s4gh

Description

@s4gh

Feature request
Documentation on how to add and support for new java versions

Please include the following information:

Is your feature request related to a problem? Please describe.
It is related to desire to add new feature in future which will leverage documentation requested here

Describe the solution you'd like.
After recent announcement here https://blogs.oracle.com/java/post/detaching-graalvm-from-the-java-ecosystem-train with explicit statements that graalvm team will focus on non java languages and that Graalvm users interested in java are encouraged to transition to openjdk it looks like future support of java by graalvm may rely on community efforts.

Graalvm is very complex technology and learning how it works for outsider is very hard and time consuming. I'd like to request a set of docs which will guide and help community members to contribute support for future java versions. I am not talking about any java specific features or optimizations but a docs to help community members to add support for Java 26, 27 and so on. Basically to help and make it easier for community to continue java language support for graalvm in future.

Describe who do you think will benefit the most.
GraalVM users will benefit. I may be wrong but even though graalvm does support not only java language I assume that wast majority of graalvm users are java developers. There are few hundred python and js developers in the company I work for. And 99.9% of them never heard of graalvm and 99.99% do not plan to change runtime for their programming language.

Describe alternatives you've considered.
I don't see realistic alternatives. I do not think volunteers could onboard and contribute anything without Graalvm team support and additional documentation.

Additional context.
https://blogs.oracle.com/java/post/detaching-graalvm-from-the-java-ecosystem-train

Express whether you'd like to help contributing this feature
If it will be feasible I may consider contributing PRs

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions