|
From: Colin S. <col...@ex...> - 2005-02-17 22:39:41
|
+1. My only concern with using the patch in JIRA vs. making a new tree of code based on existing one is if the patch has really been kept up to date properly. There have been a pretty large number of Hibernate code changes/fixes since then. It seems a shame to throw away that work, but on the other hand it might be safer to start from scratch... Colin Rod Johnson wrote: > +1 > > Dmitriy Kopylenko wrote: > >> +1 for H3 support in sandbox sooner rather then later :-) >> >> Regards, >> Dmitriy. >> >> Artur Karazniewicz wrote: >> >>> All, >>> >>> I read discussion about support for Hibernate3 (HB3 for short) last few >>> weeks, here, on dev list. I totally agree that we can wait for official >>> support of HB3 in spring till 1.2-rc versions. I wonder, though, if >>> it is >>> possible to import 'preliminary' support for HB3 into sandbox tree. >>> Since I >>> created JIRA >>> (http://opensource.atlassian.com/projects/spring/browse/SPR-300) >>> regarding >>> HB3 support and did some work integrating HB alpha release and >>> spring I got >>> *a lot* of feedback. I thing people are more and more interested in >>> support >>> for HB3 in spring, even in sandbox. Currently there are few versions of >>> patches available in SPR-300 - and it becomes harder and harder to >>> maintain >>> it. It would be nice to add support for HB3 beta in sandbox, so people >>> could just checkout it from CVS compile and use, and it would be much >>> easier to keep it in sync with rest of springframework. What about >>> that? HB3 stable will be released in 2 weeks (HB3 developers plan to >>> release >>> official stable HB3 release on JBoss World, March 1 AFAIK). >>> >>> regards, >>> Artur Karazniewicz >> |