[
https://issues.apache.org/jira/browse/KAFKA-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512040#comment-14512040
]
Ashish K Singh commented on KAFKA-2132:
---------------------------------------
Btw, looking more into it, I guess we are combining two issues here.
1. KafkaLog4jAppender is really a producer and do not belong in core. For a
user to be able to use KafkaLog4jAppender, he/she will have to pull the entire
Kafka core, which is definitely not required. This is what this JIRA is about.
2. Kafka, being a library should not depend on log4j.
I think the solution for (1) is to move the KafkaLog4jAppender to clients. For
(2), we might have to look into ways to completely get rid of log4j in Kafka
core.
> Move Log4J appender to clients 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
>
> 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)
