-
Notifications
You must be signed in to change notification settings - Fork 3.6k
HHH-15142 Reuse CriteriaQuery with explicit and implicit (=literal) params #4918
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
Conversation
…orm.junit.Jpa: Jupiter engine is not configured.
Thanks for your pull request! This pull request does not follow the contribution rules. Could you have a look? ❌ All commit messages should start with a JIRA issue key matching pattern › This message was automatically generated. |
I'm not sure, which issue key to put on 'no |
No issue key. The tests are working fine with JUnit Jupiter as you can see in the GitHub actions runs, so please revert the test changes you did and use the JUnit 5 API for new tests. |
I've downloaded the logs from your link, run More over, ci/build-github.sh delegates to ci/build.sh, which in turn just calls |
I'm working on a different solution that fixes also |
hibernate patched a "fix" which introduced a failure in their param count. params should always be explicitly annotated: hibernate/hibernate-orm#4918.
hibernate patched a "fix" which introduced a failure in their param count. params should always be explicitly annotated: hibernate/hibernate-orm#4918.
hibernate patched a "fix" which introduced a failure in their param count. params should always be explicitly annotated: hibernate/hibernate-orm#4918.
Hello Andrea |
Hi @ettavolt, I'm going to give a look at it in the next few days! |
Caused by pull request #4864.
Reverting a couple of noop changes too.
https://hibernate.atlassian.net/browse/HHH-15142