Skip to content

Fix typo in "Troubleshoot Native Image Run-Time Errors" #11406

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ In some cases, you need to provide the analysis with configuration to make all d
Failing to do so will result in an image that terminates at run-time with hard-to-diagnose errors once the dynamic feature is used in the application.
This can be avoided by eagerly checking for missing metadata.

1. Pass the `--exact-reachablity-metadata` option to the `native-image` tool and rebuild the application. If you want to do this only for a specific package, specify a package prefix `--exact-reachablity-metadata=[package prefix]`.
1. Pass the `--exact-reachability-metadata` option to the `native-image` tool and rebuild the application. If you want to do this only for a specific package, specify a package prefix `--exact-reachability-metadata=[package prefix]`.

> This option was introduced in GraalVM for JDK 23 and will become the default in the next feature release. It is equivalent to the `-H:ThrowMissingRegistrationErrors=` host option.

Expand Down Expand Up @@ -68,4 +68,4 @@ Pass the `--diagnostics-mode` option enabling diagnostics output for class initi

### Related Documentation

* [Specifying Metadata with JSON](../ReachabilityMetadata.md#specifying-metadata-with-json)
* [Specifying Metadata with JSON](../ReachabilityMetadata.md#specifying-metadata-with-json)