-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
UnresolvedElementException: Discovered unresolved method during parsing: io.netty.util.internal.logging.Log4J2Logger #5504
Comments
Hello @stephaneberle9 ,
In Quarkus only libraries covered by the Quarkus extensions are supported. For anything else there are no guarantees, so you might need to do some manual configuration to make them work. If the issue is not something you can replicate with a "simple" Java program and it only manifests in Quarkus please open an issue on https://github.com/quarkusio/quarkus instead. |
Hi @stephaneberle9 , could you please check the comment and verify if this issue is GraalVM-related or Quarkus-related? |
Yes, I've done that: It is true that there is no Quarkus extension that covers the Meanwhile, I've converted the project into plain Java (see here). Unfortunately, any attempt to compile this natively does not work either, for different reasons though. I've ended up in an endless series of "Classes that should be initialized at run time got initialized during image building: ... " errors. I've tried to cope with that by adding plenty of --initialize-at-run-time options for different problematic classes in the project dependencies (see
|
I would like to pitch in that I also encountered this issue.
Using this command:
|
Hitting the same problem, just for a different project using Google Cloud stuff, uses io.grpc's relocated Netty classes:
|
The above issues are typically resolved as described in https://quarkus.io/version/main/guides/native-reference#i-get-a-analysiserrorparsingerror-when-building-a-native-executable-due-to-an-unresolvedelementexception-what-can-i-do Note, however, that the error messages you see might be misleading due to #6253 Please try following the above guide and if you still can't resolve the issue, please consider opening a Quarkus issue with a reproducer. This doesn't seem like a GraalVM issue. |
I have come across an unexpected UnresolvedElementException for
io.netty.util.internal.logging.Log4J2Logger
while trying to generate a native image for an AWS lambda function using Quarkus and Gradle. I have isolated this problem into a trivial example project which you can find here.Steps to reproduce the issue
Build the project with
./gradlew build -Dquarkus.package.type=native -Dquarkus.native.container-build=true
GraalVM and build environment
More details
The problem as per the stack trace below comes up when adding the
software.amazon.awssdk:iotdataplane:2.18.24
dependency to thebuild.gradle
file (line 15), and goes away when removing the same.The text was updated successfully, but these errors were encountered: