在本机模式下运行 Quarkus 失败:图像生成失败。 Quarkus 原生模式是否支持 Jooq Generation

发布于 2025-01-15 10:37:27 字数 4002 浏览 4 评论 0原文

运行 ./mvnw package -Dnative 后出现此错误:

[ERROR]     [error]: Build step io.quarkus.deployment.pkg.steps.NativeImageBuildStep#build threw an exception: io.quarkus.deployment.pkg.steps.NativeImageBuildStep$ImageGenerationFailureException: Image generation failed. Exit code: 1
[ERROR]     at io.quarkus.deployment.pkg.steps.NativeImageBuildStep.imageGenerationFailed(NativeImageBuildStep.java:397)
[ERROR]     at io.quarkus.deployment.pkg.steps.NativeImageBuildStep.build(NativeImageBuildStep.java:238)
[ERROR]     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR]     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR]     at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR]     at java.base/java.lang.reflect.Method.invoke(Method.java:566)
[ERROR]     at io.quarkus.deployment.ExtensionLoader$2.execute(ExtensionLoader.java:882)
[ERROR]     at io.quarkus.builder.BuildContext.run(BuildContext.java:277)
[ERROR]     at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
[ERROR]     at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
[ERROR]     at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
[ERROR]     at java.base/java.lang.Thread.run(Thread.java:829)
[ERROR]     at org.jboss.threads.JBossThread.run(JBossThread.java:501)

我已经在本机模式下成功运行了另一个 Quarkus 项目,而没有生成 Jooq。我非常确定问题是由 Jooq 引起的。我们在 pom.xml 中以这样的方式使用 Jooq 插件:

<plugin>
               <groupId>org.jooq</groupId>
               <artifactId>jooq-codegen-maven</artifactId>
               <version>3.16.4</version>
               <executions>
                   <execution>
                       <id>jooq-codegen-exec1</id>
                       <phase>generate-sources</phase>
                       <goals>
                           <goal>generate</goal>
                       </goals>
                       <configuration>
                           <jdbc>
                               <driver>org.mariadb.jdbc.Driver</driver>
                               <url>jdbc:mariadb://127.0.0.1:3306</url>
                               <user>admin</user>
                               <password>admin</password>
                           </jdbc>
                           <generator>
                               <database>
                                   <includes>.*</includes>
                                   <inputSchema>hvb3</inputSchema>
                               </database>
                               <target>
                                   <packageName>hvbJooq</packageName>
                                   <directory>src/main/java</directory>
                               </target>
                           </generator>
                       </configuration>
                   </execution>
               </executions>
               <dependencies>
                   <dependency>
                       <groupId>mysql</groupId>
                       <artifactId>mysql-connector-java</artifactId>
                       <version>8.0.27</version>
                   </dependency>
                   <dependency>
                       <groupId>org.mariadb.jdbc</groupId>
                       <artifactId>mariadb-java-client</artifactId>
                       <version>3.0.3</version>
                   </dependency>
               </dependencies>
           </plugin>  

有人知道这个问题吗?

Running ./mvnw package -Dnative followed by this error:

[ERROR]     [error]: Build step io.quarkus.deployment.pkg.steps.NativeImageBuildStep#build threw an exception: io.quarkus.deployment.pkg.steps.NativeImageBuildStep$ImageGenerationFailureException: Image generation failed. Exit code: 1
[ERROR]     at io.quarkus.deployment.pkg.steps.NativeImageBuildStep.imageGenerationFailed(NativeImageBuildStep.java:397)
[ERROR]     at io.quarkus.deployment.pkg.steps.NativeImageBuildStep.build(NativeImageBuildStep.java:238)
[ERROR]     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR]     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR]     at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR]     at java.base/java.lang.reflect.Method.invoke(Method.java:566)
[ERROR]     at io.quarkus.deployment.ExtensionLoader$2.execute(ExtensionLoader.java:882)
[ERROR]     at io.quarkus.builder.BuildContext.run(BuildContext.java:277)
[ERROR]     at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
[ERROR]     at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
[ERROR]     at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
[ERROR]     at java.base/java.lang.Thread.run(Thread.java:829)
[ERROR]     at org.jboss.threads.JBossThread.run(JBossThread.java:501)

I've already ran another Quarkus project successfully in native mode without Jooq generation. I am very sure the problem is caused by Jooq. We are using the Jooq plugin in our pom.xml in such way:

<plugin>
               <groupId>org.jooq</groupId>
               <artifactId>jooq-codegen-maven</artifactId>
               <version>3.16.4</version>
               <executions>
                   <execution>
                       <id>jooq-codegen-exec1</id>
                       <phase>generate-sources</phase>
                       <goals>
                           <goal>generate</goal>
                       </goals>
                       <configuration>
                           <jdbc>
                               <driver>org.mariadb.jdbc.Driver</driver>
                               <url>jdbc:mariadb://127.0.0.1:3306</url>
                               <user>admin</user>
                               <password>admin</password>
                           </jdbc>
                           <generator>
                               <database>
                                   <includes>.*</includes>
                                   <inputSchema>hvb3</inputSchema>
                               </database>
                               <target>
                                   <packageName>hvbJooq</packageName>
                                   <directory>src/main/java</directory>
                               </target>
                           </generator>
                       </configuration>
                   </execution>
               </executions>
               <dependencies>
                   <dependency>
                       <groupId>mysql</groupId>
                       <artifactId>mysql-connector-java</artifactId>
                       <version>8.0.27</version>
                   </dependency>
                   <dependency>
                       <groupId>org.mariadb.jdbc</groupId>
                       <artifactId>mariadb-java-client</artifactId>
                       <version>3.0.3</version>
                   </dependency>
               </dependencies>
           </plugin>  

Does anybody know anything about this issue?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

小猫一只 2025-01-22 10:37:27

我正在使用 jOOQ Pro Java 17 和 Quarkus & GraalVM 原生模式已经在生产中使用了半年多了,但我个人并没有使用 Quarkiverse jOOQ 扩展,因为它已经过时了,并且很难与 jOOQ Express/Pro/Enterprise 一起使用。
我想保持最新状态,我最新的产品版本正在使用 Quarkus 2.9.2.Final、jOOQ Pro 3.16.6 Java 17 和 GraalVM 22.1.0 Java 17 运行。

去年为了构建微服务,我切换了从 Maven 到 Gradle,幸运的是我这样做了,所以我可以编写以下 Gradle 任务来自动注册所有 jOOQ 生成的 POJO、记录和例程在 GraalVM 构建开始之前进行 GraalVM 反射。

整个包的quarkus本机反射配置

我希望这个有帮助。

I'm using jOOQ Pro Java 17 with Quarkus & GraalVM native mode for more than half a year in production, but personally I'm not using the Quarkiverse jOOQ extension as it is outdated and is rather difficult to work with jOOQ Express/Pro/Enterprise.
I'd like to keeps things up-to-date, my latest prod build is running with Quarkus 2.9.2.Final, jOOQ Pro 3.16.6 Java 17 and GraalVM 22.1.0 Java 17.

For building the microservices last year I switched from Maven to Gradle and luckily I did so, so I could write the following Gradle task that automatically registers all jOOQ generated POJOs, Records and Routines for GraalVM reflection before the GraalVM build is started.

quarkus native reflection configuration for whole package

I hope this helps.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文