kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From viktorsomogyi <...@git.apache.org>
Subject [GitHub] kafka pull request #3477: KAFKA-1044: eliminating log4j from core
Date Mon, 03 Jul 2017 07:46:37 GMT
GitHub user viktorsomogyi opened a pull request:


    KAFKA-1044: eliminating log4j from core

    The aim of this PR to move kafka core/main away from log4j and introduce using slf4j only.
    To accomplish this task I:
    - refactored Log4jController into its own module as it is very tightly coupled with log4j
(and removing these dependencies would have been impossible without feature loss).
    - as log4j supports FATAL level but slf4j doesn't, I introduced a FATAL marker similarly
to the log4j-slf4j bridge

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/viktorsomogyi/kafka KAFKA-1044

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3477
commit 9abe1a37c2ca4f9ea95fdee394b7135ad779d971
Author: Viktor Somogyi <viktor.somogyi@cloudera.com>
Date:   2017-06-08T22:22:36Z

    KAFKA-1044: eliminating log4j from core


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message