Description
So far, Spring Data modules have required the latest Spring 3.2.x version as dependency and the modules integrate with new features available in Spring 4 in a lenient way.
However, an upgrade to Spring 4 would allow us to remove a few of these lenient checks for the Spring 4 presence and make use of new features like the @Conditional
annotation, better JDK 8 integration etc. With Spring 4.1 to be released by the time we're going to GA with the Evans release train, we'd still adhere to the "compatibility with the last but one Spring version" mantra.
Moving to Spring 4 as new baseline would also mean that the service releases for the current Spring Data Dijkstra release trains are probably maintained for a longer time than we used to do for Babbage or Codd. Still, all major new features would go into a Spring 4 based Evans.
In case you have objections to this move, feel free to elaborate on them. A plain -1 is not a convincing argument. Wouldn't mind to get supporting comments as well.