We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
GraalVM team recently announced a new release model, that will include Native Image Bundles (NIB) in the future GraalVM archives. https://medium.com/graalvm/a-new-graalvm-release-and-new-free-license-4aab483692f5
It would be nice to evaluate the impact it could have on the graalvm buildpack.
The user could create a bundle from their jar:
native-image -jar MyApp.jar -bundle-create=…/path/to/<imagename>.nib
and later on create a native image with:
native-image -bundle-apply=…/path/to/<imagename>.nib
we could decide to have the native-image buildpack support those uses cases
native-image
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the Enhancement
GraalVM team recently announced a new release model, that will include Native Image Bundles (NIB) in the future GraalVM archives. https://medium.com/graalvm/a-new-graalvm-release-and-new-free-license-4aab483692f5
It would be nice to evaluate the impact it could have on the graalvm buildpack.
Possible Solution
The user could create a bundle from their jar:
and later on create a native image with:
Motivation
we could decide to have the
native-image
buildpack support those uses casesThe text was updated successfully, but these errors were encountered: