[
https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043329#comment-16043329
]
Viktor Somogyi commented on KAFKA-1044:
---------------------------------------
@ewencp, thank you for your help.
I've started this task and all in all my conclusion is that we should delay
this until the release of slf4j 1.8 (alpha2 is already out), as there are some
log4j features that are being used but not part of slf4j, such as the
LogManager in Log4jController or the Fatal log level.
It is a bit hard to work around these effectively and without breaking
behaviour. Best I know is we could use error level instead of fatal for the
time being or we could separate off Log4jController into its own module and try
to load it in runtime if log4j is being used to get rid of the hard log4j
dependency, but these are quite hacky and I'm not sure if it's worth the effort
now as we have a workaround for the original issue. Please let me know what you
think.
> change log4j to slf4j
> ----------------------
>
> Key: KAFKA-1044
> URL: https://issues.apache.org/jira/browse/KAFKA-1044
> Project: Kafka
> Issue Type: Bug
> Components: log
> Affects Versions: 0.8.0
> Reporter: shijinkui
> Assignee: Viktor Somogyi
> Priority: Minor
> Labels: newbie
>
> can u chanage the log4j to slf4j, in my project, i use logback, it's conflict
> with log4j.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
