-
Notifications
You must be signed in to change notification settings - Fork 1.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
[native-image] should not reach here with jooby+undertow+others #749
Comments
Thank you for your report.This problem is caused by trying to build the native image with an incomplete class path, i.e., the app that you are trying to build the image from has some optional library dependencies which you probably don't use. We are currently working on a general solution for these issues and plan to release it in rc9. (For reference this seems to generate the same trace as #754.) |
@cstancu thank you for reply! Is there any way do find this dependency? |
For your app the missing class seems to be:
There is no option unfortunately to give you this information, you need to run in debug mode and know where to look or modify the source and catch the exception close to where it happens. What I did was to add:
just before the |
@cstancu looks like it makes sense to add this at least until release. Looks like nothing bad can happen because at this place native image is going to crash anyways. |
@cstancu I've added following dependencies to classpath:
|
Also I've tried just to create empty |
Closing in favor of #778 |
I'm trying to build native image from this project: https://github.com/asm0dey/school-crm
Build log is following:
To reproduce you need to perform following steps;
git clone git@github.com:asm0dey/school-crm.git
cd school-crm
mvn clean package
(optionally you can add-Dmaven.test.skip=true
or, vice versa addverify
to be sure that everything works in your environment (it should), but I'd stuck with default option)native-image -jar target/crm-1.5.0.jar
My env:
JVM version is graal rc8 ee
The text was updated successfully, but these errors were encountered: