Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix broken links in docs

Browse Source 
See gh-33209
This commit is contained in:
dreis2211
2022-11-15 22:22:02 +01:00
committed by Stephane Nicoll
parent 731797ed84
commit 3b496766da
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
spring-boot-project/spring-boot-docs/src/docs/asciidoc/native-image/advanced-topics.adoc
View File

@@ -93,7 +93,7 @@ You need to ensure that all jars are listed (the command above uses `find` and `
[[native-image.advanced.using-the-tracing-agent]]
=== Using the Tracing Agent
The GraalVM native image https://www.graalvm.org/reference-manual/native-image/Agent/[tracing agent] allows you to intercept reflection, resources or proxy usage on the JVM in order to generate the related hints.
The GraalVM native image {graal-native-image-docs}/metadata/AutomaticMetadataCollection[tracing agent] allows you to intercept reflection, resources or proxy usage on the JVM in order to generate the related hints.
Spring should generate most of these hints automatically, but the tracing agent can be used to quickly identify the missing entries.
When using the agent to generate hints for a native image, there are a couple of approaches:
@@ -128,7 +128,7 @@ To use them as input, copy them into the `src/main/resources/META-INF/native-ima
The next time you build the native image, GraalVM will take these files into consideration.
There are more advanced options which can be set on the native image tracing agent, for example filtering the recorded hints by caller classes, etc.
For further reading, please see https://www.graalvm.org/reference-manual/native-image/Agent/[the official documentation].
For further reading, please see {graal-native-image-docs}/metadata/AutomaticMetadataCollection[the official documentation].

2
spring-boot-project/spring-boot-docs/src/docs/asciidoc/native-image/introducing-graalvm-native-images.adoc
View File

@@ -27,7 +27,7 @@ The main differences are:
* There is no lazy class loading, everything shipped in the executables will be loaded in memory on startup.
* There are some limitations around some aspects of Java applications that are not fully supported.
TIP: The {graal-native-image-docs}/Limitations/[Native Image Compatibility and Optimization Guide] section of the GraalVM reference documentation provide more details about GraalVM limitations.
TIP: The {graal-native-image-docs}/metadata/Compatibility/[Native Image Compatibility Guide] section of the GraalVM reference documentation provide more details about GraalVM limitations.