Spring Framework improved its support so that Hibernate 5.2 works as well so the natural step is to support that release in Spring Boot as well.
A typical hibernate application based on JPA requires hibernate-entitymanager. One major problem we are facing is that hibernate-entitymanager is no longer required in 5.2 but no longer exists either. I don't see how we could ever support any generation before 5.2 if we bump our build to 5.2.
Our users are relying on "starters" to get the dependencies they need. We have "data-jpa" starter that brings hibernate and has an explicit reference to that artifact. We can change it but then the starter won't work < 5.2
FYI, Spring Boot has support for both 4.x and 5.x generation up to 5.1. Could you please consider adding hibernate-entitymanager again? This could be an empty artifact that depends on hibernate-core.
A typical hibernate application based on JPA requires hibernate-entitymanager
That was true prior to 5.2, yes. That is no longer the case, obviously.
I'm inclined to reject this. So far the discussion is not compelling to me from a Hibernate perspective. I can see that it causes you some difficulty in Spring Boot, though. To me you are simply hamstrung by your use of Maven here. Gradle would have let you handle this on your own.
You are lucky though and convinced me to consider adding the empty hibernate-entitymanager artifact for 5.2. I'll consider it.
Scheduled for 5.2.1 to make sure we resolve this one way or the other (reject/approve) for 5.2.1
Please don't use that as an argument to dismiss the issue. The only reason I did this is because we want RC1 to use Hibernate 5.2. I still strongly would like this issue to be fixed!