You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference-manual/native-image/BuildReport.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -203,9 +203,10 @@ After building your application, open the generated report (for example, _target
203
203
204
204
This section of the report highlights code that may require review to ensure your application runs successfully as a native executable. For example, classes loaded via `Class.forName(...)` must be included in the executable.
205
205
206
-
**Understanding the Dynamic Access tab:**
206
+
### Understanding the Dynamic Access Tab
207
207
208
208
- If no dynamic calls are detected for a class or module path entry, no further action is needed.
209
+
- If another entry provides metadata for this entry, no further investigation is needed.
209
210
- If the entry includes `native-image.properties` or `reachability-metadata.json`, or these files are provided externally, no further investigation is required.
210
211
- If integrated configuration or external metadata (such as `reflect-config.json`) exists for each detected call type, no further investigation is required.
211
212
- If none of the above apply, the entry may require further investigation.
@@ -214,6 +215,19 @@ For each entry with detected dynamic calls, you can expand the entry in the repo
214
215
215
216
> Only dynamic calls found in reachable code are reported. Some entries may have existing metadata but no reported dynamic calls.
216
217
218
+
### Dynamic Access Metadata
219
+
220
+
The Dynamic Access tab uses a `dynamic-access-metadata.json` file that maps which classpath entries provide reachability metadata for other entries. Place this file on your classpath for the Build Report to automatically discover metadata relationships between different classpath entries.
221
+
222
+
The schema includes the following keys:
223
+
224
+
*`metadataProvider`: The absolute path to the JAR or directory that provides reachability metadata
225
+
*`providesFor`: An array of classpath entries that receive metadata from this provider
226
+
227
+
For the complete JSON schema specification, see the [_dynamic-access-metadata-v1.0.0.json_ file](https://github.com/oracle/graal/blob/master/docs/reference-manual/native-image/assets/dynamic-access-metadata-v1.0.0.json){:target="_blank"}.
228
+
229
+
The Build Report uses this information to create a comprehensive view of metadata relationships and highlight potential coverage gaps.
230
+
217
231
For a practical demonstration of running and using the `-H:+ReportDynamicAccess` option, see the [preserve-package demo](https://github.com/graalvm/graalvm-demos/tree/master/native-image/preserve-package).
0 commit comments