Build error with 1.17.0 Final - quarkus + dmn + legacy jar

[Doug F]

Hi Team,

I've been trying to figure this out for some time and I think I'm stuck.

I have a simple project with only the example pricing decision table in it and GreetingResource.

It compiles and runs fine using:

mvn clean compile quarkus:dev

But when I try to build a legacy jar file using:

mvn clean compile -Pnative quarkus:build

The build fails with the following error:

[ERROR] Failed to execute goal io.quarkus.platform:quarkus-maven-plugin:2.7.2.Final:build (default-cli) on project kogito-example: Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[ERROR]         [error]: Build step io.quarkus.deployment.pkg.steps.JarResultBuildStep#buildRunnerJar threw an exception: java.lang.IllegalStateException: java.nio.file.NoSuchFileException: /META-INF/resources

If I take the pricing.dmn file out of the project, the build of the legacy jar works fine.

FYI, I added the following to the pom file, but otherwise it is as generated from the quarkus site.

        <quarkus.package.type>legacy-jar</quarkus.package.type>

I'd appreciate any guidance that could be provided.

I'm running on Windows 10, openjdk 17.0.1, maven 3.8.4

Regards,

Doug

[Matteo Mortari]

Hi Doug,

According to the Quarkus manual [1] when using GraalVM ("-Pnative") the quarkus.package.type=native

and legacy-jar doesn't seem to me to be mentioned in the supported types for Native Image generation by Quarkus.

Further, it seems you are using JDK but the Native Image profile requires you to be using GraalVM ? 🤔

In any case, in Kogito on Quarkus, we have a series of integration tests covering Native Image generation also when using the DMN extension, and without any Quarkus specific customization they work fine.

Possibly the easiest example to reference is something like the https://github.com/kiegroup/kogito-examples/tree/stable/kogito-quarkus-examples/dmn-quarkus-example

In conclusion, based on the elements provided, it seems to me you are using a combination which is not a Quarkus blueprint.

If you have a Kogito example of otherwise a standard Quarkus app which exhibit better the problem you believe affecting when using GraalVM NI, please let us know, confirming the GraalVM version you are using please

Hope this helps!

[1] https://quarkus.io/guides/building-native-image#producing-a-native-executable

--
You received this message because you are subscribed to the Google Groups "Kogito development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kogito-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kogito-development/CABz1pozhNa2GTGpN303_LfRSsuvwX-v5pf8vEBKwoVLBNwk%2BwQ%40mail.gmail.com.

--

Matteo Mortari

linkedin.com/in/matteomortari

youtube.com/MatteoMortari