2:34 p.m.
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
everybody using Spring. Spring 4 was only recently released.
IMHO this is not on the Spring team but on the fact that a significant
refactoring was executed post Hibernate 4.0.x. The corresponding Spring
JIRA is here SPR-10839 <https://jira.spring.io/browse/SPR-10839>
One idea would be to release an adapter that allows Hibernate to be used
with Spring 3.x. I'll be upgrading to Spring 4 soon, so I only care fore
convenience sake, but I control my IT infra. If you guys want the latest
and greatest Hibernate on all Spring installs this year, you might consider
helping that along a little.
Cheers,
Marc
5:47 p.m.
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 course they would have, they were looking for
traction as a new project and wanted to ride on Hibernate's popularity.
Since then, not only have they stopped reaching out to us, but in a few
cases were I reached out to them and offered suggestions on how to do
certain integrations I was ignored. So yes, in some ways it is on them.
To me, if anything, a far more compelling reason would be JPA 2.0 (4.2)
versus JPA 2.1 (4.3) support.
However, you need to understand that this is an open source project. We
simply do not have the man power that commercial offerings do. Us being
able to keep up development and testing of all these "dead" branches is
simply not feasible.
On Sat, Apr 5, 2014 at 7:34 AM, Marc Schipperheyn
<m.schipperheyn(a)gmail.com>wrote:
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
everybody using Spring. Spring 4 was only recently released.
IMHO this is not on the Spring team but on the fact that a significant
refactoring was executed post Hibernate 4.0.x. The corresponding Spring
JIRA is here SPR-10839 <https://jira.spring.io/browse/SPR-10839>
One idea would be to release an adapter that allows Hibernate to be used
with Spring 3.x. I'll be upgrading to Spring 4 soon, so I only care fore
convenience sake, but I control my IT infra. If you guys want the latest
and greatest Hibernate on all Spring installs this year, you might consider
helping that along a little.
Cheers,
Marc
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
6:58 p.m.
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
against the newer version you will receive which will indirectly impact
quality etc). I was suggesting that it might make "business sense" to keep
the support but I totally understand the need to optimize the use of
resources.
2:39 p.m.
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 <m.schipperheyn(a)gmail.com
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
soon, even though they might want to. So, this will certainly impact the
uptake of Hibernate latest version (including the amount of bug reports
against the newer version you will receive which will indirectly impact
quality etc). I was suggesting that it might make "business sense" to keep
the support but I totally understand the need to optimize the use of
resources.
3921
days inactive
3925
days old
3 comments
2 participants
participants (2)
-
Marc Schipperheyn -
Steve Ebersole