WIP

Hibernate 5 brings a breaking change by setting the
`hibernate.id.new_generator_mappings` property to `true` by default. This
does not use a sequence for a `Long` PK and therefore any SQL not
providing a value for the primary key will break.

Also, Hibernate 5 changed its naming strategy API so we'll have to detect
that in `JpaProperties#Hibernate` and set the appropriate value.

See spring-projectsgh-2763

spring-boot-dependencies/pom.xml

@@ -1455,6 +1455,11 @@
 				<artifactId>hibernate-envers</artifactId>
 				<version>${hibernate.version}</version>
 			</dependency>
+			<dependency>
+				<groupId>org.hibernate</groupId>
+				<artifactId>hibernate-java8</artifactId>
+				<version>${hibernate.version}</version>
+			</dependency>
 			<dependency>
 				<groupId>org.hibernate</groupId>
 				<artifactId>hibernate-jpamodelgen</artifactId>

spring-boot-samples/spring-boot-sample-data-jpa/pom.xml

@@ -55,4 +55,13 @@
 			</plugin>
 		</plugins>
 	</build>
+
+	<profiles>
+		<profile>
+			<id>hibernate5</id>
+			<properties>
+				<hibernate.version>5.0.1.Final</hibernate.version>
+			</properties>
+		</profile>
+	</profiles>
 </project>

spring-boot-samples/spring-boot-sample-data-jpa/src/main/resources/application.properties

@@ -1,3 +1,6 @@
 spring.h2.console.enabled=true
 
-logging.level.org.hibernate.SQL=debug
+logging.level.org.hibernate.SQL=debug
+
+
+spring.jpa.properties.hibernate.id.new_generator_mappings=false