-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
JsonNode not in Jandex after upgrade to 1.7.0.CR1 #11208
Comments
This is definitely not expected. Could you try to debug what's going on? It should pass through the If not, it might be interesting to know who created the |
A reproducer would definitely help, it's probably something related to the Kubernetes client. |
I could try to make a reproducer, but it will probably take me some time... The change I see that could affect between 1.6.1.Final and 1.7.0.CR1 is 567d9cf#diff-ededdffcf80522897a5e8aab2c124a05 but I can't be sure there is the issue. |
Good catch. Could you try that PR: #11209 ? https://github.com/quarkusio/quarkus/blob/master/CONTRIBUTING.md#checking-an-issue-is-fixed-in-master might help (but in this case, you need to get my branch from the PR) |
Yes!, it looks like your branch solves the issue. Thanks! Just a small note: |
Describe the bug
In 1.6.1.Final the maven build don't show any warning, but changing the version to 1.7.0.CR1 triggers a WARNING about
com.fasterxml.jackson.databind.JsonNode
that is not in the index.Is a multi-module project using RESTEasy, so I would assume there is the ignore for ReflectiveHierarchyStep set.
Expected behavior
No log warning message.
Actual behavior
To Reproduce
** Not sure how to reproduce it easily **
Environment (please complete the following information):
uname -a
orver
: Linux qk 5.4.0-42-generic Add proper logging #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linuxjava -version
: OpenJDK Runtime Environment GraalVM CE 20.1.0 (build 11.0.7+10-jvmci-20.1-b02)mvnw --version
orgradlew --version
): 3.6.3The text was updated successfully, but these errors were encountered: