Don't mention HHH-17362 in migration guide

It's not a solution, see https://hibernate.atlassian.net/browse/HHH-17362?focusedCommentId=113465
This commit is contained in:
Yoann Rodière 2023-12-04 09:16:32 +01:00 committed by GitHub
parent 80e148b37b
commit 6e7e83277d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions

View File

@ -78,8 +78,9 @@ To get rid of that error:
1. Check out the specific sections in the User Guide for a guideline on how to properly harness the annotation processor classpath to use `hibernate-jpamodelgen`: 1. Check out the specific sections in the User Guide for a guideline on how to properly harness the annotation processor classpath to use `hibernate-jpamodelgen`:
see {userGuideBase}#tooling-gradle-modelgen[here for Gradle] or {userGuideBase_6_4}#tooling-maven-modelgen[here for Maven]. see {userGuideBase}#tooling-gradle-modelgen[here for Gradle] or {userGuideBase_6_4}#tooling-maven-modelgen[here for Maven].
2. If the annotation processor classpath doesn't work in your case (e.g. because you use Maven and need the version of `hibernate-jpamodelgen` managed through a BOM), 2. If the annotation processor classpath doesn't work in your case because you use Maven and need the version of `hibernate-jpamodelgen` managed through a BOM,
upgrade to a newer version of Hibernate ORM that fixes https://hibernate.atlassian.net/browse/HHH-17362[HHH-17362]. watch for new releases of the Maven Compiler Plugin, which should handle dependency management for `annotationProcessorPath` entries in version 3.12.0;
see https://issues.apache.org/jira/browse/MCOMPILER-391.
[[hql-null-literal-comparison]] [[hql-null-literal-comparison]]
== HQL null literal comparison == HQL null literal comparison