-
Notifications
You must be signed in to change notification settings - Fork 89
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
Build fails if quarkus-oidc-client
is not in the classpath
#824
Comments
@rmanibus, since you introduced this feature, do you mind taking a look and fixing it if possible? |
Sure ! |
@rmanibus do you have an estimate when you can take a look at it? |
I tried to poke around already, I think I have a solution but I am still trying to find a way to test it. I am not sure how I could remove an extension for a specific test. |
You can create a new |
I tried that already, but the oidc extension is included in the parent pom, and there is no way to exclude it |
yes |
Il still have an issue with 2.6.0 and 2.6.0-lts linked, i think, with oidc client. I have this warning and after that, the test is blocked indefinitely : |
Could you provide a reproducer ? |
Same issue here Java 17 You can reproduce it with a fresh Quarkus projets |
@rmanibus mind taking a look? |
@rmanibus facing the same issue. The blocked start seems to be triggered by having quarkus-hibernate-validator as dependency in the project. Reproducer: unpack, and simply execute mvn quarkus:dev. Does not start. |
@rmanibus, did you have the chance to take a look at it? @Postremus I'm busy with #852. As soon as I fix it (it was more challenging than I first foresaw), I'll fix this one, too, if the original author of the feature cannot. |
I will have a look over the weekend, sorry I am pretty busy this week ! |
Reopening this issue since we are still getting many complains from the community after this change. I'll work on it this week cc @gastaldi |
Quarkus core issue: quarkusio/quarkus#44689 |
It seems that a few extensions are triggering this problem. The file |
…ity dependencies Signed-off-by: Ricardo Zanini <[email protected]>
@oben01 @Postremus @vhuc @vkn can you please try this PR on your end? #872 |
@ricardozanini works for me |
Works for me also thank u |
…ncies (#872) * Fix #824 - Introduce a separated OIDC module to hold security dependencies Signed-off-by: Ricardo Zanini <[email protected]> * Fix parent module Signed-off-by: Ricardo Zanini <[email protected]> --------- Signed-off-by: Ricardo Zanini <[email protected]>
…ncies (#872) * Fix #824 - Introduce a separated OIDC module to hold security dependencies Signed-off-by: Ricardo Zanini <[email protected]> * Fix parent module Signed-off-by: Ricardo Zanini <[email protected]> --------- Signed-off-by: Ricardo Zanini <[email protected]>
…ncies (#872) (#874) * Fix #824 - Introduce a separated OIDC module to hold security dependencies * Fix parent module --------- Signed-off-by: Ricardo Zanini <[email protected]> Co-authored-by: Ricardo Zanini <[email protected]>
As part of the build generation introduced in #795, the latest release now breaks projects that are not using OIDC:
This openAPI spec doesn't even have
security
tags, so all the authz classes should be skipped and not generated.The text was updated successfully, but these errors were encountered: