On Wed, 02 May 2012 21:15:06 -0300, Kalle Korhonen
<kalle.o.korho...@gmail.com> wrote:
On Wed, May 2, 2012 at 5:00 PM, Kalle Korhonen
<kalle.o.korho...@gmail.com> wrote:
Sounds like we should back out the hibernate version change then. We
might need to create a separate java 6 version of tapestry-hibernate
(we could use classifiers to separate the artifacts at least for
Maven), can I assume you'll sign up to work on it?
I apologize, I mean a separate tapestry-hibernate4 artifact and we
shouldn't use classifiers for differentiation.
That's what I suggested in the mailing list. :P As far as I know (I
haven't had the chance to test Hibernate 4 yet), it's not backward
compatible with Hibernate 3.x and the tapestry-hibernate version which
supports H4 needed some changes, so it seems to me tapestry-hibernate
supporting H3.x doesn't work with H4 and tapestry-hibernate supporting H4
doesn't work with H3.x.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
