From e02ed9d4d15ef8e7d8fa8e75665eca1130e5d321 Mon Sep 17 00:00:00 2001 From: Gail Badner Date: Wed, 28 Nov 2018 15:29:26 -0800 Subject: [PATCH] HHH-13126 : Update README and migration notes to indicate changes in Java compatibility --- README.md | 3 ++- migration-guide.adoc | 11 ++++++++++- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 33624df43f..d839219e41 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,8 @@ Quickstart cd hibernate-orm ./gradlew clean build -The build requires a Java 8 JDK as JAVA_HOME, but will ensure Java 6 compatibility. +The build requires a Java 8 JDK as JAVA_HOME. Versions up through 5.1.3.Final ensure Java 6 compatibility. +Versions up through 5.1.16.Final ensure Java 7 compatibility. As of 5.1.17.Final, Java 8 is required. Resources diff --git a/migration-guide.adoc b/migration-guide.adoc index 3ab9d42cb0..1b12d9401c 100644 --- a/migration-guide.adoc +++ b/migration-guide.adoc @@ -42,8 +42,17 @@ This strategy may require `hibernate.default_schema` and/or `hibernate.default_c To use the old strategy, which executes a `java.sql.DatabaseMetaData#getTables(String, String, String, String[])` call for each javax.persistence.Entity, use the property setting `hibernate.hbm2ddl.jdbc_metadata_extraction_strategy=individually`. +== Changes to Java compatibility -=== Many-to-one association in embeddable collection elements and composite IDs +Versions 5.1.0.Final through 5.1.3.Final ensure Java 6 compatibility. + +Versions through 5.1.16.Final ensure Java 7 compatibility. + +As of 5.1.17.Final, Java 8 is required. + +See details on the https://hibernate.atlassian.net/browse/HHH-13126[HHH-13126] Jira issue. + +== Many-to-one association in embeddable collection elements and composite IDs A bug introduced in 4.3 caused many-to-one associations in embeddable collection elements and composite IDs to be eagerly fetched, even when explicitly mapped as lazy.