Upgraded minimum Hibernate required version to 4.3. Removed Travis build profiles for everything below that. Upgraded to Spring Framework 5.0 snapshots.
Removed integration test execution for OpenJPA for now as Spring Framework 5 doesn't ship OpenJpaVendorAdapter anymore as there's no JPA 2.1 compatible OpenJPA version available currently.
Upgraded to Spring Data build parent and Commons in 2.0. No upgrade to Spring 5 yet as it requires Hibernate 5 which currently breaks our tests, mostly because of [0].
Added workaround for compiler ambiguities that stem from the upgrade to 1.8 as compile target [1]. Temporarily removed tests for JpaSort for the same reason.
Adapted to API changes in DefaultResourceLoader in preparation of the move to Spring 5.
[0] https://hibernate.atlassian.net/browse/HHH-10690
[1] http://mail.openjdk.java.net/pipermail/compiler-dev/2016-November/010521.html
We now use a completely reflective lookup of the Hibernate query string as well as for the Hibernate specific PersistenceProvider lookup in tests.
Added build profile for Hibernate 5.2 but it's currently not working due to Hibernate complaining about an invalid identifier mapping on CustomAbstractPersistable which is overriding the parent types property on accessor working fine on 5.1.
The build profile for 5.1 is still broken due to the fixed but yet unreleased HHH-10514 [0] and the not yet fixed HHH-10515 [1] (apparently fixed but still open and unreleased) which has been broken since 5.0.8.
[0] https://hibernate.atlassian.net/browse/HHH-10514
[1] https://hibernate.atlassian.net/browse/HHH-10515
Upgraded to OpenJPA 2.4.1 and Hibernate 4.2 build profile to 4.2.1. Added more snapshot profiles and register them for execution in the Travis build (Hibernate 4.2.next, 4.3.next, 5.next, 5.1, 5.1.next, Eclipselink.next and EclipseLink 2.7.next). Disabled Bundlor plugin for Travis build to make sure the OSGi-incompatible Eclipselink snapshot version numbers don't break the build.
To make sure the coverage data is collected for all test executions, we now explicitly add the Jacoco Java agent to the test executions.
Added Jacoco plugin explicitly to make sure the agent can be resolved even if the build is not run in sonarcube profile.
