After much investigation, the move of EAP 7.1 to Hibernate ORM 5.2 was judged too risky as some non trivial application changes could have been required by customers. Our fallback plan is to embed Hibernate ORM 5.1.x instead.

The main features of this upgrade are:

• Ad-hoc entity joins
• API for loading by multiple ids in batch
• Envers audit queries now can refer to to-one association

are related to a customer demand.

see http://in.relation.to/2016/02/10/hibernate-orm-510-final-release/ for high level details and the changelog for full details https://hibernate.atlassian.net/browse/HHH-10971?jql=project%20%3D%20HHH%20AND%20fixVersion%20in%20(5.1.1%2C%205.1.2%2C%205.1.0)

Note that this means that gbadner@redhat.com will need to resuscitate the 5.1.x branch and apply the necessary fixes.
Also a corresponding EAP7 issue should be opened for Hibernate Search to keep with the various fixes and improvements.

See corresponding Wildfly issue https://issues.jboss.org/browse/WFLY-6854