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 2014/09/24 07:30:34 UTC

[jira] [Commented] (KAFKA-1645) some more jars in our src release

    [ https://issues.apache.org/jira/browse/KAFKA-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145919#comment-14145919 ] 

Jun Rao commented on KAFKA-1645:
--------------------------------

For all the jars under migration tool, they are used for system tests. Now that 0.8 has been out for a year. I fell there is not a strong need to maintain the migration tool for much longer.  We can probably just remove the migration tool test suite. For the piggybank jar, it's used only in hadoop-producer. piggybank-0.12.0.jar is available in maven and seems to work with the hadoop producer code. We can just remove the jar and add the dependency to piggybank in the build.gradle file.

> some more jars in our src release
> ---------------------------------
>
>                 Key: KAFKA-1645
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1645
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Joe Stein
>            Priority: Blocker
>             Fix For: 0.8.2
>
>
> The first one is being taken care of in KAFKA-1490 
> the rest... can we just delete them? Do we need/want them anymore? 
> {code}
> root@precise64:~/kafka-0.8.1.1-src# find ./ -name *jar
> ./gradle/wrapper/gradle-wrapper.jar
> ./lib/apache-rat-0.8.jar
> ./system_test/migration_tool_testsuite/0.7/lib/kafka-0.7.0.jar
> ./system_test/migration_tool_testsuite/0.7/lib/kafka-perf-0.7.0.jar
> ./system_test/migration_tool_testsuite/0.7/lib/zkclient-0.1.jar
> ./contrib/hadoop-consumer/lib/piggybank.jar
> ./contrib/hadoop-producer/lib/piggybank.jar
> {code}
> rat is not required in the project I can speak for that file +1 to remove it
> I don't see why we have to keep the other ones nor what code changes we have to make for getting rid of them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)