If you are wondering how this relates to the geode-log4j work that Kirk did, the following diagram might help. Basically, he made a geode-log4j module that makes log4j-core optional. This geode-logging module allows the use of some of our log4j wrapper classes from modules other than geode-core.
[image: image.png] On Thu, Sep 26, 2019 at 11:26 AM Ernest Burghardt <eburgha...@pivotal.io> wrote: > Dear Geode, > > In support of the Membership > < > https://cwiki.apache.org/confluence/display/GEODE/Move+membership+code+to+a+separate+gradle+sub-project > > > modularization efforts, we would like to move some of our logging code that > wraps log4j into a separate module is needed in order to break dependencies > on geode-core. > > The proposed module <https://issues.apache.org/jira/browse/GEODE-7177> > would be called "geode-logging" and would contain LogService, > LoggingThread, LoggingExecutor and related classes. > > As always, your feedback is welcomed and appreciated. > > Ernie and Dan >
