You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2015/07/07 01:37:05 UTC

[jira] [Updated] (KAFKA-2132) Move Log4J appender to a separate module

     [ https://issues.apache.org/jira/browse/KAFKA-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jun Rao updated KAFKA-2132:
---------------------------
       Resolution: Fixed
         Reviewer: Jun Rao  (was: Jay Kreps)
    Fix Version/s: 0.8.3
           Status: Resolved  (was: Patch Available)

Thanks for the latest patch. +1 and committed to 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
>             Fix For: 0.8.3
>
>         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, KAFKA-2132_2015-06-24_10:19:56.patch, KAFKA-2132_2015-06-24_10:25:43.patch, KAFKA-2132_2015-06-30_12:07:23.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)