Yes, I agree it is a shame.
BTW, did you see we just released yet another 4.2? ;)
On Mon, Apr 7, 2014 at 11:58 AM, Marc Schipperheyn wrote:
> Fair enough. It's a shame though. Like it or not, there are tons of people
> using Spring and I'm guessing the vast majority will not be on 4.0 any time
Fair enough. It's a shame though. Like it or not, there are tons of people
using Spring and I'm guessing the vast majority will not be on 4.0 any time
soon, even though they might want to. So, this will certainly impact the
uptake of Hibernate latest version (including the amount of bug reports
aga
I simply do not consider Spring a valid reason to keep older Hibernate
release families active. So to say its "not on the Spring team" and imply
it is all Hibernate's problem is a bit misleading. Early in
Spring/Hibernate integration they used to work with us to flesh out
integration points. Of
Just wanted to outline some reasons for keeping the Hibernate 4.2.x release
train alive.
I would love to update today to 4.3.x. But I'm on Spring 3.x and the
Hibernate 4.3.x line only made it into Spring 4.x. So everybody using
Spring 3.x will be stuck on 4.2.x. I would say that's prob just about
