[
https://issues.apache.org/jira/browse/KAFKA-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513061#comment-14513061
]
Jay Kreps commented on KAFKA-2132:
----------------------------------
Hey [~singhashish], I think I may have caused confusion.
The current state is
clients--depends on slf4j not log4j
core--depends on log4j
I think the log4j in core is okay because it mostly gets run as a service
rather than embedded library (though that does happen too).
People were very, uh, vocal about the desire to not have the client package
depend on log4j. We can't move this appender class to the clients package
without reintroducing the log4j dependency and incurring the wrath of the java
logging people. :-)
I recommend we make a stand-alone module called log4j/ that has this one class.
It is a bit silly to have a single class in its own module, but I think that
does address the goal of this ticket. I recommend we also move the class to
Java so people don't have the scala dependency either.
Thoughts?
> 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)
