Why is Micronaut AOT enabled per default in newly generated applications using the Micronaut CLI? #9826
-
I'm wondering why Micronaut AOT is enabled per default in newly generated Micronaut 4 projects, when the documentation says it is an experimental project and using it is at your own risk? Is the project no longer experimental, and the documentation just not up-to-date, or? Also - this is how the
But I can't find any description of the different features in the documentation main page or the configuration reference (which is empty). Thanks in advance for enlightening me 🙂 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
fwiw the options are described a bit better in https://micronaut-projects.github.io/micronaut-gradle-plugin/latest/#_micronaut_aot_plugin . and the aot integration will only run if you use on the 'optimized' targets (e.g. nativeOptimizedCompile instead of nativeCompile) |
Beta Was this translation helpful? Give feedback.
@melix
fwiw the options are described a bit better in https://micronaut-projects.github.io/micronaut-gradle-plugin/latest/#_micronaut_aot_plugin . and the aot integration will only run if you use on the 'optimized' targets (e.g. nativeOptimizedCompile instead of nativeCompile)