Skip to content

Commit ab96849

Browse files
committed
Document how to handle the manifest in a native image with Maven
Closes gh-42412
1 parent d44e7c9 commit ab96849

File tree

1 file changed

+6
-0
lines changed
  • spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc

1 file changed

+6
-0
lines changed

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

+6
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,12 @@ The `native` profile configures the following:
3737
** Validate that a suitable GraalVM version is available.
3838
** Download third-party reachability metadata.
3939

40+
[WARNING]
41+
====
42+
The use of the raw classpath means that native image does not know about the generated `MANIFEST`.
43+
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.
44+
====
45+
4046
To benefit from the `native` profile, a module that represents an application should define two plugins, as shown in the following example:
4147

4248
[source,xml,indent=0,subs="verbatim,attributes",tabsize=4]

0 commit comments

Comments
 (0)