Configuring the native build
In Chapter 6, Building a Native Image, we went over the necessary steps to package our backend Quarkus application into a native executable. With the recent changes we’ve made to include the frontend resources and the new GatewayResource class, we’ll need to add further modifications to the native configuration so that everything works as expected. Let’s start by configuring the native build so that it accounts for the frontend resources.
Including the frontend resources
In the Including application resources section of Chapter 6, Building a Native Image, we learned that the GraalVM native image uses AOT compilation and performs an aggressive static code analysis to find what resources, classes, methods, and so on should be included in the resulting binary image. We also learned that we can manually include additional resources by using the quarkus.native.resources.includes property. However, to include the frontend resources...
