You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Aaron Lindsey (Jira)" <ji...@apache.org> on 2019/09/11 15:46:00 UTC
[jira] [Commented] (GEODE-7177) Move membership's logging
dependencies to its own module
[ https://issues.apache.org/jira/browse/GEODE-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927705#comment-16927705 ]
Aaron Lindsey commented on GEODE-7177:
--------------------------------------
There is an open PR to move classes that depend on log4j-core to a submodule: [https://github.com/apache/geode/pull/4003]. That might be relevant to this issue. You may want to coordinate with [~klund] as he is in the process of refactoring a large amount of logging code.
> Move membership's logging dependencies to its own module
> --------------------------------------------------------
>
> Key: GEODE-7177
> URL: https://issues.apache.org/jira/browse/GEODE-7177
> Project: Geode
> Issue Type: Improvement
> Components: logging, membership
> Reporter: Ryan McMahon
> Assignee: Ryan McMahon
> Priority: Major
>
> As part of eliminating membership's dependency on geode-core, we want to move LogService and some other supporting classes to its own module which membership can depend on.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)