Re: ssl configuration parameters

A correction is needed here, this seems to actually work. The catch is that if a JmxOperationInvoker is created from a client with a “ssl- enabled-components” scope broader than the one defined on the locators and servers, it seems to override it “cluster” scope. Is this behavior expected? On Th

Lingering Geode 1.10.0 release issues

If you try and brew update to Geode 1.10.0 you won't get it until our 1.10.0 homebrew PR gets through their checks and their Jenkins servers seem to be having problems this week so this is still in flight. On geode develop I've had to revert t

Re: Lingering Geode 1.10.0 release issues

Bruce has picked up GEODE-7250. -Dan On Fri, Sep 27, 2019 at 9:27 AM Dick Cavender wrote: > If you try and brew update to Geode 1.10.0 you won't get it until our > 1.10.0 homebrew PR > gets > through their checks and their Jenkins servers s

Re: Lingering Geode 1.10.0 release issues

Did the 'merge release branch into master and develop' go smoothly? On Fri, Sep 27, 2019 at 9:27 AM Dick Cavender wrote: > If you try and brew update to Geode 1.10.0 you won't get it until our > 1.10.0 homebrew PR > gets > through their chec

Re: Lingering Geode 1.10.0 release issues

Some backward-compatibility tests are using string comparisons on versions, which isn't working well with our new "1.10.0".  Others are converting version strings into numbers, so 1.10.0 becomes 1100.  That's working okay but is also a time-bomb.  I'm changing the tests to use a new TestVersion

Re: Lingering Geode 1.10.0 release issues

Unfortunately I'm finding that our gradle build scripts are also using string comparisons on Geode versions.  You can't do something like     (oldGeodeVersion >= "1.7.0") and expect that to work when the version is "1.10.0" On 9/27/19 10:12 AM, Bruce Schuchardt wrote: Some backward-compatibili

Cutting Geode 1.9.2

Hi there Geode Dev's, There seems to be consensus on cutting Geode 1.9.2. https://lists.apache.org/thread.html/9b5f5c58e1b298d9d0ca870a0deec06f7344a60809790c75a5f68bfa@%3Cdev.geode.apache.org%3E Would there be any willing candidates who would raise their hand to shepherd this release? Maybe s

re: broken build

I've pushed changes to handle v1.10.0 in our tests Please don't push changes to our repo w/o running them through our tests. You might think changing something like setting.gradle isn't a big deal but in this case it exposed problems that needed to be addressed.

Re: broken build

Thanks Bruce! I’ve updated the release script to make a PR instead of committing directly to develop when adding the old version. > On Sep 27, 2019, at 5:04 PM, Bruce Schuchardt wrote: > > I've pushed changes to handle v1.10.0 in our tests > > Please don't push changes to our repo w/o running