You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ashish K Singh (JIRA)" <ji...@apache.org> on 2015/06/14 06:20:01 UTC
[jira] [Commented] (KAFKA-2132) Move Log4J appender to a separate
module
[ https://issues.apache.org/jira/browse/KAFKA-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584931#comment-14584931 ]
Ashish K Singh commented on KAFKA-2132:
---------------------------------------
Updated reviewboard https://reviews.apache.org/r/33614/
against branch trunk
> Move Log4J appender to a separate module
> ----------------------------------------
>
> Key: KAFKA-2132
> URL: https://issues.apache.org/jira/browse/KAFKA-2132
> Project: Kafka
> Issue Type: Improvement
> Reporter: Gwen Shapira
> Assignee: Ashish K Singh
> Attachments: KAFKA-2132.patch, KAFKA-2132_2015-04-27_19:59:46.patch, KAFKA-2132_2015-04-30_12:22:02.patch, KAFKA-2132_2015-04-30_15:53:17.patch, KAFKA-2132_2015-06-13_21:18:59.patch
>
>
> Log4j appender is just a producer.
> Since we have a new producer in the clients module, no need to keep Log4J appender in "core" and force people to package all of Kafka with their apps.
> Lets move the Log4jAppender to clients module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)