Build failed in Jenkins: Geode-nightly #981

See Changes: [github] GEODE-1290: AbstractRegionEntry.prepareValueForCache cache the new [github] GEODE-3785: correctly update the schema version, namespace and lcoati… [browe] GEODE-3751: a single place for client

Re: [DISCUSS] C++ Returning null values

To me the question of a no-op region comes down to whether customers would need to do logic based on whether a region has a parent. If they do, perhaps a bool hasParent() along with getParent() returning a no-op region would be an elegant solution. If they do not, then shared_ptr is probably suf

Build failed in Jenkins: Geode-nightly-flaky #146

See Changes: [browe] GEODE-3751: a single place for client protocol loading, logic. [huynhja] GEODE-3714: Removed repetitive looping code when evaluating [kohlmu-pivotal] GEODE-3802: moved Authenticator and A

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #706 was SUCCESSFUL (with 2182 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #706 was successful. --- Scheduled 2184 tests in total. https://build.spring.io/browse/SGF-NAG-706/ -- This

Thinking about a "Public API" module

Hi all, I'm thinking about the possibility of making a "Geode public API" module, mostly containing interfaces that Geode implements. Why would one do this, you may ask? Here are some reasons. * It makes clear what is our public API (as opposed to "internal" type packages). * Users only have to

Re: Thinking about a "Public API" module

Yes! Do it! Even if it can’t be complete at this time because of strange dependencies we should start the effort. You might just start with some common use APIs like listeners and functions. At least in that case if all your hat is going to reference is functions and listeners you don’t have t

[Discuss] Geode gradle plugin

Hi all, I've been working on a Gradle plugin to make it easier to write integration tests for applications that use Apache Geode, and would like to discuss where it should reside. To give some background, we have a JUnit Rule called GfshRule that lets you write tests that execute gfsh comman

Re: 1.3.0 release

All issues targeted for 1.3.0 have been resolved. I will cut a release candidate shortly. On Sat, Oct 7, 2017 at 11:18 AM Swapnil Bawaskar wrote: > Hi All, > Thanks for all your efforts in resolving a whopping 51 issues in the past > week! Since I did not hear any concerns, I removed 1.3 label f