-
Notifications
You must be signed in to change notification settings - Fork 39
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
Maven native build proposal #93
Comments
Do you mean a build for GraalVM? The backend of the demo application for the library (https://github.com/manuelbl/SwissQRBillDemo/tree/master, published at https://www.codecrete.net/qrbill/) actually uses a native build. It is built on top of the Quarkus framework. AWT is known to be a challenge with GraalVM. The Quarkus people built a special addition that takes care of it. In the demo application, it's configured here: https://github.com/manuelbl/SwissQRBillDemo/blob/master/service/pom.xml#L54 If you are also using Quarkus, that should help. If you don't use it, the extension might help you to understand what's needed to get it running. |
Exactly, GraalVM build. I am running quarkus also. I believe I once tried to use quarkus-awt dependency to bypass this, but it resulted in the same error. I will try it again just for good measure. |
You might want to look at this commit. It contains the relevant changes. The changes for Java classes in the namespace |
Yes, I understand that, and I tried it following the changes made in the provided commit, but I am still getting an issue with a bunch of classes being inited at build time instead of runtime. |
Could the library be adapted to work in maven native build?
Currently it's not working due to java.awt not being fully supported:
org.jboss.resteasy.spi.UnhandledException: java.lang.InternalError: java.lang.ClassNotFoundException: sun.awt.X11FontManager
The text was updated successfully, but these errors were encountered: