-
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
Warning since 3.13.0: Failed to index org.jboss.resteasy.annotations.cache.NoCache #42413
Comments
Maybe related to some jandex change? /cc @Ladicek |
My guess is that it's going to be hard to pinpoint the culprit without a reproducer. |
Mmmmh but you are only using RESTEasy Reactive here, right? I don't see any RESTEasy Classic artifact. |
Exactly! I find that rather puzzling. |
It seems to me that the It doesn't seem like a Jandex issue, especially since Jandex wasn't updated between 3.12.0 and 3.13.0. |
I think it would help if you could figure out where this annotation comes from. |
@Ladicek I wonder if we should improve the callers to log where the annotation was found so that things are a bit more actionable? |
That sounds like a good idea, but the method that logs the warning is only called from an implementation of |
@famod I'm going to close this one. If you can debug it and get us more information, please reopen and I will have a look. |
Funnily, I've just found the same warning multiple times in the Quarkus CI (e.g. JVM Tests - JDK 21). I'll gather some affected tests. |
So it seems to be coming from some Keycloak dependency. |
I was able to find a single usage of that annotation in the keycloak codebase: https://github.com/keycloak/keycloak/blob/main/integration/admin-client/src/main/java/org/keycloak/admin/client/resource/ClientTypesResource.java#L27 Which makes sense given that |
It seems the class with that annotation was added in KC 25.0.0: keycloak/keycloak@3fffc51#diff-cfcc9e857008e4393a63a51cada94d238d4aecd610d4742fde9965fa0f4ef754R27 And Quarkus updated to 25.0.0 in 3.13.0.CR1: #41162 |
I flagged this as an upstream keycloak issue, although I'm not entirely sure whether Quarkus dependency management has something to do with it. |
I created keycloak/keycloak#32731 |
Fixed in 3.15.1 via Update to Keycloak 25.0.6. Thanks everyone! |
👌 |
Describe the bug
I'm getting
in various (but not all) modules of my quarkus app repo (which actually builds three different app flavors).
This is the full message from one of the affected tests (but I also see this warning in dev mode and when building the respective quarkus app in two of the three flavors/modules):
Expected behavior
No such warning, just like in 3.12 and before.
Actual behavior
Warning is logged.
How to Reproduce?
n/a ATM
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
3.13.0.CR1, 3.13.0, 3.13.1
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
mvn quarkus:dependency-tree
of one of the affected modules:The text was updated successfully, but these errors were encountered: