-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Provide a user-facing API to deal with GraalVM options #1605
Comments
Maybe some of this should be driven by config, e.g. file globs for matching resources to keep in the final image. Also it would be nice to align some of this between JVM mode and native image, for example if I want to have some resource available at run time, I should be able to just specify that I want that resource instead of having extra config for native image. Non-included resources should be excluded from both JVM mode and native image. The closer we make the experience between the two, the easier it will be for users to move from JVM to native image in their dev cycle. |
See https://stackoverflow.com/questions/55300484/how-to-include-classpath-resources-in-a-quarkus-native-image/55300914#55300914 for a user asking about that. |
Seems to be coming up a lot lately :) |
As a Maven user, I would expect all my Maven resources from the current reactor to be included in the final image (otherwise, I wouldn't put them in the reactor in the first place), and of course I wouldn't want to worry about any patterns to match exactly my resources and nothing else from the classpath, so it would be really nice if quarkus-maven-plugin could do the job for me. |
Resources are addressed more specifically in #2746. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you! |
hello, I have try to list all option, that I found in release note of graal:
Seems not needed:
|
For extension developers, we have all the
BuildItem
machinery which takes care of configuring GraalVM.For applications themselves, we expose
@RegisterForReflection
but that's pretty much it. There's a need for a user-facing API allowing to configure GraalVM from the application code itself (add resources, resource bundles...).The text was updated successfully, but these errors were encountered: