-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for GraalVMs native-image #1243
Comments
A PR would be welcome! |
@choubuzhaole I cannot see any reference to Apache Shiro in the graalvm-reachibility-metadata repository. Are sure that there is some Apache Shiro related content? |
Hello, my description is wrong, there is indeed no reference to apache shiro in graalvm-reachability-repository. That’s why it asks whether it supports graalvm |
Currently I'm trying to use graalvm to compile my project into an executable versiongraalvm: graalvm-community-jdk-21.0.1 It compiles fine and when I launch the executable I get the following problem
|
Search before asking
Feature Request
Hi!
Oracle has created the GraalVM and one of its features is the 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, resources and proxies.
Luckily, a library can ship some JSON metadata in the META-INF/native-image/... 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, 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.
We are hardly waiting for GrallVM native-image support in officially Shiro repository.
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: