Correct. Put it on a feature branch awaiting contributions.
On 23/09/2016 8:41 AM, Anthony Baker wrote:
By remove, do you mean “put it on a feature branch awaiting contributions?”
hibernate-3.5.5 was released in 2010 and has undergone significant changes
since then. Seems reasonable to put this feature on hold until can be brought
current.
Anthony
On Sep 22, 2016, at 3:31 PM, Udo Kohlmeyer <ukohlme...@pivotal.io> wrote:
+1 to removing until updated to newer version
Do we know if anyone in the big-bad world is using it?
--Udo
On 23/09/2016 8:15 AM, William Markito wrote:
Folks,
We're still building the Hibernate cache module [1] but it's compatible
only with a very old version (3.5) and given that the API has completely
changed and unless someone in the community wants to help getting this
module up-to-date with at least Hibernate 5.x I'd like propose to remove
the module from 1.0 / develop until we can work on updating that module.
Given that it's already a separate module it shouldn't be that hard to be
removed.
Thoughts ?
[1]
http://geode.docs.pivotal.io/docs/tools_modules/hibernate_cache/chapter_overview.html
