renyijiu
commented
2 years ago I also asked a related question in jooq, https://github.com/jOOQ/jOOQ/issues/13550
Open renyijiu opened 2 years ago
renyijiu
commented
2 years ago I also asked a related question in jooq, https://github.com/jOOQ/jOOQ/issues/13550
lukaseder
commented
2 years ago I also asked a related question in jooq, jOOQ/jOOQ#13550
In that issue, I suggested you try working with the quarkiverse/quarkus-jooq third party contribution. However, you seem to have posted the exact same error report.
Have you changed your setup to use quarkiverse/quarkus-jooq yet, or have you just re-posted your error report here without changing anything?
gsmet
commented
2 years ago The problem is using EE 10 dependencies: jakarta.xml.bind:jakarta.xml.bind-api:4.0.0.
You should stick to the dependencies brought by the io.quarkus:quarkus-jaxb extension until Quarkus moves to EE 10.
renyijiu
commented
2 years ago I also asked a related question in jooq, jOOQ/jOOQ#13550
In that issue, I suggested you try working with the
quarkiverse/quarkus-jooqthird party contribution. However, you seem to have posted the exact same error report.Have you changed your setup to use
quarkiverse/quarkus-jooqyet, or have you just re-posted your error report here without changing anything?
@lukaseder I'm missing some of the information, I've used the relevant dependencies and these errors are generated on top of that
implementation 'io.quarkus:quarkus-jdbc-postgresql'
implementation "io.quarkiverse.jooq:quarkus-jooq:${quarkusJooqVersion}"
implementation "org.postgresql:postgresql:${postgresqlDriverVersion}"@renyijiu If the problem mentioned by @gsmet is the one causing this:
The problem is using EE 10 dependencies: jakarta.xml.bind:jakarta.xml.bind-api:4.0.0.
Then, I guess you should stick with jOOQ 3.15, for now?
renyijiu
commented
2 years ago The problem is using EE 10 dependencies:
jakarta.xml.bind:jakarta.xml.bind-api:4.0.0.You should stick to the dependencies brought by the
io.quarkus:quarkus-jaxbextension until Quarkus moves to EE 10.
I didn't add jakarta.xml.bind:jakarta.xml.bind-api:4.0.0 this dependency in the project. I just tried to add the dependency to solve the problem, but it didn't work. The same project compiles successfully with graalvm version 22.0.0.2, but with version 22.1, the above error message is displayed.
renyijiu
commented
2 years ago The relevant dependency information is as follows
| +--- jakarta.xml.bind:jakarta.xml.bind-api:2.3.3 (c)
....
| \--- org.jooq:jooq:3.15.5 -> 3.16.6
| +--- io.r2dbc:r2dbc-spi:0.9.0.RELEASE
| | \--- org.reactivestreams:reactive-streams:1.0.3
| \--- jakarta.xml.bind:jakarta.xml.bind-api:3.0.0 -> 2.3.3
| \--- jakarta.activation:jakarta.activation-api:1.2.2 -> 1.2.1
...
jooqGenerator - The classpath used to invoke the jOOQ code generator. Add your JDBC driver, generator extensions, and additional dependencies here.
+--- org.jooq:jooq-codegen -> 3.16.6
| +--- org.jooq:jooq:3.16.6
| | +--- io.r2dbc:r2dbc-spi:0.9.0.RELEASE
| | | \--- org.reactivestreams:reactive-streams:1.0.3
| | \--- jakarta.xml.bind:jakarta.xml.bind-api:3.0.0
| | \--- com.sun.activation:jakarta.activation:2.0.0
| \--- org.jooq:jooq-meta:3.16.6
| \--- org.jooq:jooq:3.16.6 (*)
+--- org.jooq:jooq-meta-extensions:3.16.6
| +--- org.jooq:jooq-meta:3.16.6 (*)
| \--- com.h2database:h2:2.1.210 -> 2.1.212
\--- com.h2database:h2:2.1.212@lukaseder @gsmet
https://github.com/renyijiu/quarkus-jooq-issue-demo I build a demo project, run ./gradlew build -Dquarkus.package.type=native will get the same errors.
apatrida
commented
2 years ago @renyijiu the problem is that you are using libraries that are not compatible. You cannot use JOOQ 3.16.x yet, and will have to wait for Quarkus 2.10.0 to be able to combine the two. Any fix for the incompatibility is outside the scope of this project for which you are reporting an issue.
Basically, you have done something that won't work, and want their help fixing it. Instead, use JOOQ 3.15.5 and don't upgrade it until later.
Note the nu.studer.jooq code generation Gradle plugin must be reverted to 6.0.1 as well when using JOOQ 3.15.5.
An alternative is also to not use native images until these libraries are all compatible again or you figure out how to hack in dependencies.
renyijiu
commented
2 years ago @renyijiu the problem is that you are using libraries that are not compatible. You cannot use JOOQ 3.16.x yet, and will have to wait for Quarkus 2.10.0 to be able to combine the two. Any fix for the incompatibility is outside the scope of this project for which you are reporting an issue.
Basically, you have done something that won't work, and want their help fixing it. Instead, use JOOQ 3.15.5 and don't upgrade it until later.
Note the
nu.studer.jooqcode generation Gradle plugin must be reverted to 6.0.1 as well when using JOOQ 3.15.5.An alternative is also to not use native images until these libraries are all compatible again or you figure out how to hack in dependencies.
Thanks for your answer, it works well on graalvm version 22.0.0.2, I will keep this version for now and wait for the new release to test and verify again
uPagge
commented
1 year ago @renyijiu Is there any news on this issue? Faced the same error
renyijiu
commented
1 year ago @renyijiu Is there any news on this issue? Faced the same error
graalvm 22.3, quarkus 2.14.1 still build with same error
Your question:
I have built a project with Quarkus framework and JOOQ library for database connection that runs with GraalVM native-image. When I compile natively, I get some jooq-related error messages, and I can't be sure if the missing dependencies are the cause. Run
./gradlew clean build -Dquarkus.package.type=nativeand the error message is as follows:Versions:
Not effective solution
Add the
dependencies in the project, and it seems nothing changed, still get errors.Is there something I'm missing? Thanks.
When i test with GraalVM CE 22.0.0.2, it successful create the native execute file.