Skip to content

Explore the impact of new GraalVM defaults on Quarkus #44864

@zakkak

Description

@zakkak

Description

oracle/graal#10178 changes some defaults around reachability metadata, namely:

  1. All reflectively-accessed types now have all their fields registered for runtime access by default
  2. All reflectively-accessible classes are now registered for unsafe allocation
  3. All serializable types can now be serialized with all possible constructors

The goal of this issue is to track the impact of this changes on the Quarkus core integration tests to see if/when Quarkus should opt-out of these new defaults.

Implementation ideas

The new changes are being tested in https://github.com/graalvm/mandrel/actions/runs/12114945249 (with collector API tag graal-pr-10178-reachability-test) and will be compared to the results of https://github.com/graalvm/mandrel/actions/runs/12114969951 (with collector API tag graal-pr-10178-reachability-test-before)

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions