-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Error generating native-image with --allow-incomplete-classpath #900
Comments
I am unable to replicate this while using the example code in #812 , Micronaut 1.0.3, latest GraalVM master, i.e., GraalVM Version 1.0.0-rc12-dev, and labsjdk1.8.0_192-jvmci-0.53 as my base JDK. |
Actually you're right. I have repeated all steps one more time and it also works for me using the same versions as you. The only difference was that I was using Just to make sure I'm doing everything right for the future, this is what I do to compile everything:
Are these the right steps to build everything? Another question. In the Micronaut sample application we have
What I've done is publish locally the latest jars and use them:
And then I update the dependency in
And build the fatjar again and the native-image. I was wondering if this is really necessary. Thank you very much for your time and sorry for the noise. |
We should increase the minimum JVMCI required version from 50 to 53. @dougxc recently made some changes on the JVMCI side to help with our efforts to fix the incomplete classpath issues. The steps you use to build are correct, however you don't need to run Your Regarding the
The I hope I answered all your questions. We will try to make all this more explicit in our documentation. I will close this issue now. |
@cstancu Thank you very much for your detailed explanation. Now I understand a little bit more how this works! |
This is related to #812. I've tried with latest GraalVM
master
and also with tagrelease/graal-vm/1.0
(that currently is rc11-snapshot) and when building the native image I get the following exception:The text was updated successfully, but these errors were encountered: