CI failure

Hi, For some reason the CI that was triggered after I committed my changes failed on the following - error: cannot find symbol @ConfigAttributeGetter(name = THREAD_MONITOR_AUTO_ENABLED) ^ This symbol is well defined under - ConfigurationProperties Also I did no

Geode Build Changes Incoming -- Take care during merging!

Hello, all, from your friendly neighborhood spotless-purveyor. With PR#1926, wildcard imports will be prohibited by spotless in accordance with our style guide. As a gradle change, this presents the higher-than-typical possibility that a PR with a green precheckin and successful build could fa

Re: CI failure

Hi Yossi, Well, this one is confusing! Your branch builds fine for me too. BUT, travis is not building your branch. It actually builds a *merge* of your branch with develop. Which I guess the travis-ci people thought was cool, but makes things really confusing in cases like this. Your code doesn

Geode unit tests completed in 'develop/UITests' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/317

[Proposal] Publicizing Extension et al for future consumption by the experimental Configuration Persistence Service (previously "Cluster Configuration Service")

Hello, all! I was in the process of writing a Wiki entry [1] on my experience in using the experimental cluster configuration API. While making an explicit distinction between the configuration class and any object(s) that configuration class would create, I discovered that the Extension interf

Geode unit tests completed in 'develop/UITests' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/319

Re: [Proposal] Publicizing Extension et al for future consumption by the experimental Configuration Persistence Service (previously "Cluster Configuration Service")

My vote would be to keep it as is: 1. It's going to be replaced anyway. 2. we've been living with this flaw(extension modules has to use an internal api) since day one, might as well live with it for a little longer before we replace it with a more preferred api. but I can be convinced otherwise.

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

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

Request to edit / comment on Geode Confluence

Hi Geode Dev, I would like to comment on a few of the Apache Geode proposals on Confluence. Can someone help me with the permissions? I currently cannot comment. Thank you, Addison