On Wed, 13 Jan 2016 10:49:41 -0200, Ido Dovrat <ido.dov...@gmail.com>
wrote:
Hibernate is not a dependency of Tapestry. The integration is provided
as a separate module. There is no surefire way to make such a module
compatible across all version combinations (tapestry and hibernate).
Agreed, even if I understand Jens' opinion.
I think tapestry-hibernate should always be aligned with the latest
version of Hibernate (currently 5.x). If possible, it should also
support earlier
versions of Hibernate, but only to a point and not at all costs.
Considering the non-backward-compatible changes between Hibernate major
versions (3 vs 4 vs 5), I don't know how supporting more than one version
in the same codebase could work.
All other users are free to fork the module and adapt it to their special
needs.
tapestry-hibernate and tapestry-hibernate-core are small pieces of code,
so forking is definitely viable.
Legacy support of ancient versions is not a common use scenario.
Agreed. According to https://en.wikipedia.org/wiki/Hibernate_(framework),
Hibernate 4.0.0 was released on December 2010, more than 5 years ago,
which is a lot for the quick pace of software development.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
