root
/
spring-boot
mirror of https://github.com/spring-projects/spring-boot.git
1
0
Fork 0
Code Issues Actions 12 Packages Projects Releases Wiki Activity

Document how to handle the manifest in a native image with Maven 

Closes gh-42412
This commit is contained in:
Stéphane Nicoll 2024-09-30 10:55:37 +02:00
parent d44e7c9af2
commit ab968494e6
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/aot.adoc
View File

@ -37,6 +37,12 @@ The `native` profile configures the following:
** Validate that a suitable GraalVM version is available. ** Validate that a suitable GraalVM version is available.
** Download third-party reachability metadata. ** Download third-party reachability metadata.
[WARNING]
====
The use of the raw classpath means that native image does not know about the generated `MANIFEST`.
If you need to read the content of the manifest in a native image, for instance to get the implementation version of your application, configure the `classesDirectory` option to use the regular jar.
====
To benefit from the `native` profile, a module that represents an application should define two plugins, as shown in the following example: To benefit from the `native` profile, a module that represents an application should define two plugins, as shown in the following example:
[source,xml,indent=0,subs="verbatim,attributes",tabsize=4] [source,xml,indent=0,subs="verbatim,attributes",tabsize=4]