-
Notifications
You must be signed in to change notification settings - Fork 3k
Upgrade to Hibernate Validator 9.0 #42292
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
Upgrade to Hibernate Validator 9.0 #42292
Conversation
b214566
to
c303b6b
Compare
🙈 The PR is closed and the preview is expired. |
@marko-bekhta thanks for this! Apart from the the PR needing to be rebased, is there anything more that needs to be done in order for it to be considered ready? |
Hey @geoand 👋🏻 😃 From the Validator's perspective, there are no more updates to apply at the moment. As to marking it ready for a review ... there are probably a few things to consider:
|
c303b6b
to
f91ddee
Compare
I see, thanks for the update! I'll let @gsmet comment further, since he is the SME on this :) |
f91ddee
to
324ad68
Compare
If we want this, it will need a rebase |
324ad68
to
7d3598c
Compare
My take on this is that it's nice to have the PRs ready but I'd like to sync things a bit and preferably move everything we can to Jakarta EE 11 at the same time. Let's keep this PR open (and updated when new releases come out) and we can decide later what to do with it. |
👍🏻 that makes sense 😃 And as for the HV itself ... we still would need a final release of Expressly, but there's no news on when that could happen 😕 |
7d3598c
to
a77999d
Compare
@marko-bekhta I'm willing to open the gate for EE 11 integration now that ORM 7 is close to completion. If you can revive this PR, I think we can get it in for 3.23. |
a77999d
to
0a9dd22
Compare
rebased 😃🤞🏻 |
So Jakarta 11 is still not released? We had some people pushing us to do the move as it was supposed to be released (at least the important part). |
a jakartaee-bom final bom was publihsed on 2025-03-12 (https://central.sonatype.com/artifact/jakarta.platform/jakarta.jakartaee-bom/11.0.0) |
Any update on this? The reason I am asking is that I would like to have this so we can close our only bug left from 2019 😆 |
mmmm 2019 😃 😌
I'm ready to do a 9.0.0.Final even today 🙈 but the problem is still with the missing Expressly 6.0.0 Final 😕 https://jakarta.ee/specifications/expression-language/6.0/ suggests that Tomcat is a compatible EL implementation 🙈 but IDK if we'd want to switch from Expressly to Tomcat in Quarkus 🙈 (it's probably this one:https://central.sonatype.com/artifact/org.apache.tomcat/tomcat-jasper-el/overview) |
I see, thanks! |
0a9dd22
to
69359d2
Compare
Let's wait for Expressly, we are in no hurry. |
69359d2
to
9446252
Compare
ha 😃 https://repo1.maven.org/maven2/org/glassfish/expressly/expressly/6.0.0/ |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
9446252
to
37cf4cc
Compare
I took the liberty to rebase the PR onto |
thanks 😃 |
👍🏽 |
Status for workflow
|
Status for workflow
|
Status | Name | Step | Failures | Logs | Raw logs | Build scan |
---|---|---|---|---|---|---|
✔️ | JVM Tests - JDK 17 | Logs | Raw logs | 🔍 | ||
✔️ | JVM Tests - JDK 21 | Logs | Raw logs | 🔍 | ||
✖ | JVM Tests - JDK 17 Windows | Build |
Failures | Logs | Raw logs | 🔍 |
✖ | JVM Integration Tests - JDK 17 | Build |
Failures | Logs | Raw logs | 🔍 |
✔️ | JVM Integration Tests - JDK 17 Windows | Logs | Raw logs | 🔍 | ||
✔️ | JVM Integration Tests - JDK 21 | Logs | Raw logs | 🔍 |
Full information is available in the Build summary check run.
You can consult the Develocity build scans.
Failures
⚙️ JVM Tests - JDK 17 Windows #
- Failing: extensions/vertx-http/deployment
! Skipped: devtools/bom-descriptor-json devtools/cli extensions/agroal/deployment and 147 more
📦 extensions/vertx-http/deployment
✖ io.quarkus.vertx.http.proxy.TrustedForwarderDnsResolveTest.testTrustedProxyResolved
- History - More details - Source on GitHub
java.io.IOException:
Error while binding on /127.0.0.1:53530
original message : Address already in use: bind
at org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:238)
at org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:51)
at org.apache.mina.core.polling.AbstractPollingIoAcceptor.registerHandles(AbstractPollingIoAcceptor.java:585)
at org.apache.mina.core.polling.AbstractPollingIoAcceptor.access$400(AbstractPollingIoAcceptor.java:71)
at org.apache.mina.core.polling.AbstractPollingIoAcceptor$Acceptor.run(AbstractPollingIoAcceptor.java:459)
⚙️ JVM Integration Tests - JDK 17 #
- Failing: integration-tests/observability-lgtm
📦 integration-tests/observability-lgtm
✖ Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.5.2:test (default-test) on project quarkus-integration-test-observability-lgtm:
See /home/runner/_work/quarkus/quarkus/integration-tests/observability-lgtm/target/surefire-reports for the individual test results.
See dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
There was an error in the forked process
Flaky tests - Develocity
⚙️ JVM Tests - JDK 21
📦 extensions/infinispan-cache/deployment
✖ io.quarkus.cache.infinispan.InfinispanCacheTest.testGetAsyncWithParallelCalls
- History
expected: "thread1" but was: "thread2"
-org.opentest4j.AssertionFailedError
org.opentest4j.AssertionFailedError:
expected: "thread1"
but was: "thread2"
at io.quarkus.cache.infinispan.InfinispanCacheTest.testGetAsyncWithParallelCalls(InfinispanCacheTest.java:283)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at io.quarkus.test.QuarkusUnitTest.runExtensionMethod(QuarkusUnitTest.java:521)
at io.quarkus.test.QuarkusUnitTest.interceptTestMethod(QuarkusUnitTest.java:435)
⚙️ Maven Tests - JDK 17
📦 integration-tests/devmode
✖ io.quarkus.test.devui.DevUIGrpcSmokeTest.testTestService
- History
Too many recursions, message not returned for id [966390518]
-java.lang.RuntimeException
java.lang.RuntimeException: Too many recursions, message not returned for id [966390518]
at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:168)
at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
⚙️ JVM Integration Tests - JDK 17
📦 integration-tests/opentelemetry
✖ io.quarkus.it.opentelemetry.LoggingResourceTest.testException
- History
Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes.
-org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
at io.quarkus.it.opentelemetry.LoggingResourceTest.testException(LoggingResourceTest.java:113)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
⚙️ JVM Integration Tests - JDK 21
📦 integration-tests/opentelemetry
✖ io.quarkus.it.opentelemetry.LoggingResourceTest.testException
- History
Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes.
-org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
at io.quarkus.it.opentelemetry.LoggingResourceTest.testException(LoggingResourceTest.java:113)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
Opening as a draft, as this is a Beta release only.