-
Notifications
You must be signed in to change notification settings - Fork 17
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
Doesn't compile in native mode with GraalVM 22.1 #73
Comments
Regarding this particular problem, the dependency on pgjdbc has been removed again in jOOQ 3.17 via shading of this particular class, see jOOQ/jOOQ#13053 Obviously, preventing such issues by building jOOQ for GraalVM as well would be better. It will happen in the future, not sure when: jOOQ/jOOQ#8779 |
Another way would be to include substitutions in the jOOQ extension that will explicitly make the optional dependencies unreachable.
That would be the best things to do. |
@lukaseder found another issue when trying to use jOOQ 3.16.x that uses Jakarta... Jakarta is listed as provided, but the references are there... for instance in checks if Jakarta is present by using an imported class instead of using a string as class name... and there are other places... if Jakarta is required, it shouldn't be listed as provided in the pom... or the code should be refactored... if doing graalvm substitution for this one, will have to create a large one |
@luneo7 from the specs: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
Seems like we're doing everything right. |
GraalVM 22.1 introduced
--link-at-build-time
and Quarkus 2.9.2.Final enforces its use unless you use the dreprecatedNativeImageAllowIncompleteClasspathBuildItem
to disable that feature.jOOQ has incomplete class path (optional dependencies) that causes the build to fail if linked at build time, we should either add a
NativeImageAllowIncompleteClasspathBuildItem
so we can do native image with jOOQ, and/or fix jOOQ upstream so DB utils are in a separated lib that needs to be imported if using the desired DB.This is the stack trace of trying to build jOOQ in GraalVM 22.1
The text was updated successfully, but these errors were encountered: