choubuzhaole opened a new issue, #1243: URL: https://github.com/apache/shiro/issues/1243
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/shiro/issues?q=is%3Aissue) and found no similar issues. ### Feature Request Hi！ Oracle has created the [GraalVM](https://www.graalvm.org/) and one of its features is the [native-image](https://www.graalvm.org/22.2/docs/getting-started/#native-image) tool, which allows compiling a JVM application into a native executable. This executable doesn't need a JVM to run, it starts faster and often consumes less memory. But this has downsides, as some dynamic features from Java are not supported without additional configuration. The biggest contenders are [reflection](https://www.graalvm.org/22.2/reference-manual/native-image/dynamic-features/Reflection/), [resources](https://www.graalvm.org/22.2/reference-manual/native-image/dynamic-features/Resources/) and [proxies](https://www.graalvm.org/22.2/reference-manual/native-image/dynamic-features/DynamicProxy/). Luckily, a library can ship some JSON metadata in the [META-INF/native-image/...](https://www.graalvm.org/22.2/reference-manual/native-image/metadata/) directory which enables those features. For libraries which don't (or can't) add the metadata in their JARs, Oracle has created the [graalvm-reachability-repository](https://github.com/oracle/graalvm-reachability-metadata), which contains this metadata outside of the libraries JAR file. In an ideal world, all of the metadata is moved into the JARs of the libraries, but until our world has reached its ideal state, this repository will be used. There's already metadata for your library [in this repository](https://github.com/oracle/graalvm-reachability-metadata/tree/master/metadata/org.flywaydb/flyway-core), but it would be great if in future this metadata would reside directly in your codebase. The big advantage is that if your code changes, the metadata can change along with it. Otherwise users would be broken until the graalvm-reachability-metadata is updated. What do you think? Are you willing to put this metadata in your codebase? If you have more questions about native-image, please don't hesitate to ask. Hi! We are hardly waiting for GrallVM native-image support in officially Shiro repository. ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
