You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2017/03/10 18:21:04 UTC
[jira] [Updated] (GEODE-2237) Geode classes should use Log4J2
Logger instead of JUL or LogWriter
[ https://issues.apache.org/jira/browse/GEODE-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirk Lund updated GEODE-2237:
-----------------------------
Summary: Geode classes should use Log4J2 Logger instead of JUL or LogWriter (was: Geode product classes should use Log4J2 Logger instead of JUL or LogWriter)
> Geode classes should use Log4J2 Logger instead of JUL or LogWriter
> ------------------------------------------------------------------
>
> Key: GEODE-2237
> URL: https://issues.apache.org/jira/browse/GEODE-2237
> Project: Geode
> Issue Type: Bug
> Components: logging
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Labels: Log4j2
>
> Several classes including AbstractLauncher are using JUL instead of Log4J2:
> {noformat}
> import java.util.logging.Logger;
> ...
> // TODO: use log4j logger instead of JUL
> protected Logger logger = Logger.getLogger(getClass().getName());
> {noformat}
> Any other classes that are using a logger or logwriter that isn't from Log4J2 API should be modified to use Log4J2.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)