We recommend that you follow the instructions and create the application step-by-step. The goal is to show users the difference, and prove how using shared metadata can simplify the work. This guide demonstrates how to build a native executable with the Tracing agent and using the GraalVM Reachability Metadata Repository. Autodetecting (if the required resources are directly available on the classpath, in the src/main/resources directory)įor the Java application used in this guide the first two approaches are applicable.Using the shared GraalVM Reachability Metadata Repository.Native Image loads classes dynamically at build time, and not at run time.ĭepending on your application dependencies, there are three ways to provide the metadata with the Native Image Gradle Plugin: In the real-world, your application will, most likely, call either Java Reflection, Dynamic Proxy objects, or call some native code, or access resources on the class path - dynamic features that the native-image tool must be aware of at build time, and provided in the form of metadata. If the application does not dynamically load any classes at run time, then your workflow is just one command. The plugin is provided as part of the Native Build Tools project and uses the Gradle build tool. With the Gradle plugin for GraalVM Native Image you can easily build a native executable from a Java application. JavaScript must be enabled to correctly display this contentĬonfigure Native Image Using Shared Reachability Metadata
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |