-
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
1.13.4 backports 1 #17125
1.13.4 backports 1 #17125
Conversation
(cherry picked from commit e4fc5f7)
(cherry picked from commit 5cb8c3c)
(cherry picked from commit a4d7742)
(cherry picked from commit 2dd4726)
(cherry picked from commit 23a7cf8)
This reworks the test so that Person (an Entity class) no longer uses j.u.Random directly, but delegates generation of random data to a separate class which gets runtime-initialized. Closes quarkusio#16018 (cherry picked from commit b12f825)
(cherry picked from commit 94aa129)
Bumps [jackson-bom](https://github.com/FasterXML/jackson-bom) from 2.12.1 to 2.12.3. - [Release notes](https://github.com/FasterXML/jackson-bom/releases) - [Commits](FasterXML/jackson-bom@jackson-bom-2.12.1...jackson-bom-2.12.3) Signed-off-by: dependabot[bot] <support@github.com> (cherry picked from commit 8ddadbb)
(cherry picked from commit 7720e8d)
…DC providers which do not fill "username", falls back to "sub" instead (cherry picked from commit f075bf8)
When a user set `quarkus.http.test-port=0` or `quarkus.http.quarkus.http.test-ssl-port=0`, there is no way to know the port number to expose when launching the container, therefore we need to resort to selecting the random port(s) in the test before launching the container Fixes: quarkusio#16900 (cherry picked from commit 47ee7e4)
(cherry picked from commit 784ab49)
This is done in order to stay in line with what Quarkus allows when using RESTEasy Classic Fixes: quarkusio#16934 (cherry picked from commit 46a41de)
…rces (cherry picked from commit 434eada)
(cherry picked from commit 2f6c5c0)
(cherry picked from commit 3a2ecd9)
Even if the superclass is not ann application class if the generated bytecode references application classes then it may be nessesary for the synthetic bean to be an application class. (cherry picked from commit 96574d0)
(cherry picked from commit 4be9cef)
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 7965097
Full information is available in the Build summary check run. Test Failures⚙️ JVM Tests - JDK 11 #📦 integration-tests/oidc-client-wiremock✖ ⚙️ JVM Tests - JDK 11 Windows #📦 integration-tests/oidc-client-wiremock✖ ⚙️ JVM Tests - JDK 15 #📦 integration-tests/oidc-client-wiremock✖ ⚙️ JVM Tests - JDK 8 #📦 integration-tests/oidc-client-wiremock✖ ⚙️ Native Tests - Security2 #📦 integration-tests/oidc-client-wiremock✖ |
(cherry picked from commit a6188af)
Fixes: quarkusio#16905 (cherry picked from commit d621f8d)
Closes quarkusio#16338 (cherry picked from commit 77669cf)
Fixes quarkusio#17086 (cherry picked from commit 9d987ab)
(cherry picked from commit f96633d)
Fixes quarkusio#16768 (cherry picked from commit ba938ce)
Please don't merge, I will merge it myself.