-
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
Main entry point not found when using library flying-saucer-pdf !?!? #3148
Comments
I am not able to reproduce the problem on a simple project. Maybe the error pops up by mixing several libraries. Problem is that the error doesn't give any hint on the problem... :-( |
Could you please provide a working reproducer for this issue? |
Sorry, but I cannot reproduce it on a simple project, and I cannot give you the entire project. I guess you can close the ticket. Who knows maybe someone will have the same problem! |
I am running into this error when I add this library ('org.xhtmlrenderer', 'flying-saucer-pdf', '9.1.20') implementation group: 'com.lowagie', name: 'itext', version: '2.1.7', ext: 'pom' any thoughts ? |
Not sure whether you're using Quarkus 2.8 and above. If yes, the best way to deal with this is to import all the required libs to ensure the class path is complete at build time. You can refer to the pom.xml of the flying-saucer-pdf library itself. For my case, I would need to add in these three libs to build the native image successfully |
Thank you @wushuartgaro. Your comment so far is the only working version and solution i've found for quarkus. All new versions cannot pass Quarkus's validations. I believe they've started using language features that are not supported by GraalVM. Even trying to move all the checks to runtime does not help. With this version and dependencies list it works. |
Describe the issue
I am using GraalVM for a long time with several dependencies (such as AWS...). But as soon as I am using the dependency 'org.xhtmlrenderer:flying-saucer-pdf:9.1.20' the native compilation fails in a very weird way:
I have isolated the problem: I have commented all code which use this library. Even though, simply by adding this dependency in the gradle build script, it raises this very strange error.
Steps to reproduce the issue
Describe GraalVM and your environment:
More details
All the option (--native-image-info, --verbose, and H:+ReportExceptionStackTraces) don't give anymore info.
The text was updated successfully, but these errors were encountered: