[
https://issues.apache.org/jira/browse/KAFKA-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505329#comment-14505329
]
Jay Kreps commented on KAFKA-2132:
----------------------------------
Yeah it definitely makes sense to move the log4j appender out of core. I don't
think we should add it to clients, though, as clients currently depends on
slf4j (the whole point of which is to avoid a direct log4j dependency).
Arguably the whole java logging thing is silly since everyone ends up depending
on log4j in the end anyway, but I guess for appearances sake we should try not
to be the library that causes that? :-)
So I think maybe just making a separate log4j module is the best approach? Kind
of silly to have a whole jar with just one class but I guess I don't see
another option.
> 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)
