There appears to be consensus that this is a critical fix. The following commit has been brought into release/1.12 as the critical fix for GEODE-7776:
git cherry-pick -x 7ab2713d6c9d2d09a986513aaa18b333951fe61e GEODE-XXXX has been marked as 'resolved in' 1.12. Regards EB On Wed, Feb 12, 2020 at 10:37 AM Dick Cavender <dcaven...@pivotal.io> wrote: > Ernie- Can you please cherry-pick GEODE-7776 to release/1.12.0? > > > On Tue, Feb 11, 2020 at 11:45 AM Jinmei Liao <jil...@pivotal.io> wrote: > >> +1 >> >> On Tue, Feb 11, 2020, 11:39 AM Udo Kohlmeyer <u...@apache.com> wrote: >> >> > +1 >> > >> > On 2/11/20 11:23 AM, Dick Cavender wrote: >> > > This regression was introduced when the geode-gfsh subproject was >> > recently >> > > added. While not obvious this created a critical build / runtime cycle >> > > between geode-core and geode-gfsh that causes some tools/IDEs, that >> don't >> > > cope well with circular dependencies, to fail. Additionally no >> previous >> > > Geode releases have shipped with known circular dependencies. >> > > >> > > commit 7ab2713d6c9d2d09a986513aaa18b333951fe61e >> > > Author: Robert Houghton <rhough...@pivotal.io> >> > > Date: Mon Feb 10 13:18:34 2020 -0800 >> > > >> > > GEODE-7776 - Proposed changes to remove build cycle (#4679) >> > > >> > > * Proposed changes to remove build cycle >> > > >> > > * Fix expected pom, and delete commented dependency >> > > >> > >> >
