I've created a ticket (feel free to modify/reword/rename it). It's
GEODE-1972: Move Geode Hibernate module to a feature branch
On Thu, Oct 6, 2016 at 10:17 AM Dave Barnes wrote:
So, what form should the JIRA ticket assume?
(a) Move HIbernate from develop to a feature
So, what form should the JIRA ticket assume?
(a) Move HIbernate from develop to a feature branch, or
(b) Merge Hibernate code to develop (as a future task, cf GEODE-1416 for
how the NC was handled)
After somebody (which I can do, if you like) creates a ticket for the code,
I'll create a subtask
+1 for moving to a feature branch.
On Thu, Oct 6, 2016 at 9:32 AM Mark Bretl wrote:
> +1 for feature branch as well.
>
> --Mark
>
> On Thu, Oct 6, 2016 at 9:30 AM, Dan Smith wrote:
>
> > +1 for moving it to a feature branch.
> >
> > -Dan
> >
> > On Wed,
+1 for feature branch as well.
--Mark
On Thu, Oct 6, 2016 at 9:30 AM, Dan Smith wrote:
> +1 for moving it to a feature branch.
>
> -Dan
>
> On Wed, Oct 5, 2016 at 2:40 PM, Jason Huynh wrote:
> > Bumping to see if we have come to a decision on whether we
+1 for moving it to a feature branch.
-Dan
On Wed, Oct 5, 2016 at 2:40 PM, Jason Huynh wrote:
> Bumping to see if we have come to a decision on whether we want to move
> this to a feature branch and get rid of it for 1.0 or post 1.0, especially
> now that the 1.0 release
Bumping to see if we have come to a decision on whether we want to move
this to a feature branch and get rid of it for 1.0 or post 1.0, especially
now that the 1.0 release branch has been cut
On Fri, Sep 23, 2016 at 5:22 PM Anthony Baker wrote:
Likewise! Geode provides an L2
Likewise! Geode provides an L2 cache for Hibernate. That is, an application
that is using Hibernate could plug in Geode for caching. Specifically, we
implement Hibernate’s cache interfaces like CacheProvider, RegionFactory, etc.
There are build-time dependencies on several hibernate jars
Geode provides an optional L2 cache for hibernate:
http://geode.docs.pivotal.io/docs/tools_modules/hibernate_cache/setting_up_the_module.html
Looking at the code, it looks like the geode-modules-hibernate is pulling
in hibernate-core as a compile dependency, but it's not being distributed
as
Note: Doc situation is similar to that of JVSD, except there are more docs
for Hibernate.
On Thu, Sep 22, 2016 at 3:55 PM, William Markito
wrote:
> If moving to a feature branch is a better approach, I'm fine as well..
>
> On Thu, Sep 22, 2016 at 3:45 PM, Udo Kohlmeyer
If moving to a feature branch is a better approach, I'm fine as well..
On Thu, Sep 22, 2016 at 3:45 PM, Udo Kohlmeyer
wrote:
> 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
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
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
+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
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
14 matches
Mail list logo