-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
org.apache.log4j.Priority required via netty, although netty should not be in the class path at all #17461
Labels
kind/bug
Something isn't working
Comments
@aloubyansky could you help with this? It looks like a classpath issue? |
I'll have a look. |
The dependency on |
This is not looking good. |
It's Camel Quarkus issue apache/camel-quarkus#2683 |
Thanks a lot, Alexey and sorry for the false alarm! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Copied from apache/camel-quarkus#2670
After the upgrade to Quarkus 2.0.0.Alpha3 (this may have been the case also with previous milestones, we do not know), the native compilation started failing in
integration-tests/aws2
- see the error message bellow.org.apache.log4j.Priority
seems to be required only throughio.netty.util.internal.logging.Log4J2Logger
innetty-common
, but netty should not be there in the class path at all. None of the runtime dependencies requires it directly or indirectly.The
dependency:tree
shows that netty-common is only pulled viaio.quarkus:quarkus-junit5:jar:2.0.0.Alpha3:test
, so I guess it should really not end up inquarkus-app/lib/main
where it is seen by native compiler.Workaround: add
io.quarkus:quarkus-resteasy
to the test module.Steps to reproduce:
The text was updated successfully, but these errors were encountered: