Re: [DISCUSS] Logging module separation

[Jacob Barrett]

It is so great to see all the modules finally spinning out.  Make it so!!

-Jake

> On Sep 26, 2019, at 11:26 AM, Ernest Burghardt  wrote:
> 
> Dear Geode,
> 
> In support of the Membership
> 
> 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 
> 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

Re: [DISCUSS] Logging module separation

[Dan Smith]

Sorry Anil. Maybe this will work -
https://cwiki.apache.org/confluence/x/cRLABw

-Dan

Re: [DISCUSS] Logging module separation

[Anilkumar Gingade]

Dan, Some reason, cant view the diagram...It doesn't show up...


On Thu, Sep 26, 2019 at 11:52 AM Dan Smith  wrote:

> 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 
> 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 
>> 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
>>
>

Re: [DISCUSS] Logging module separation

[Dan Smith]

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 
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 
> 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
>

[DISCUSS] Logging module separation

[Ernest Burghardt]

Dear Geode,

In support of the Membership

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 
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