Skip to content

Conversation

@Ostrzyciel
Copy link
Member

Closes #128

Turns out that the Google proto classes require reflection for text serialization -- this was something that scalapb did not require.

To fix this, we could hardcode the methods and classes that need to have reflective access enabled, but it would be a mess to maintain. Instead, we have a custom Graal feature that discovers the needed classes and registers them for reflective access.

Closes #128

Turns out that the Google proto classes require reflection for text serialization -- this was something that scalapb did not require.

To fix this, we could hardcode the methods and classes that need to have reflective access enabled, but it would be a mess to maintain. Instead, we have a custom Graal feature that discovers the needed classes and registers them for reflective access.
Copy link
Collaborator

@Karolina-Bogacka Karolina-Bogacka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aside from a tiny spelling error everything looks fine

@Ostrzyciel Ostrzyciel enabled auto-merge (squash) May 31, 2025 11:06
@Ostrzyciel Ostrzyciel merged commit 03faeba into main May 31, 2025
7 checks passed
@Ostrzyciel Ostrzyciel deleted the GH-128/fix-aot-jelly-text branch May 31, 2025 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

jelly-text output not working in 0.4.4 AOT build

3 participants