hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12556) KafkaSink jar files are created but not copied to target dist
Date Fri, 26 Feb 2016 10:36:18 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168800#comment-15168800

Steve Loughran commented on HADOOP-12556:

I'd like it so that if you explicitly ask for hadoop-kafka then you get everything you need.
My own concerns are to make sure that if you depended on core stuff (hadoop-client), you don't
get another set of classpath problems. And we have so much cruft (why does junit get into
mapreduce/lib? Because it did in the past and if you pull it now, things break ... )

You're talking about hadoop-tools-dist, aren't you? If so, where do the JARs end up on a release

> KafkaSink jar files are created but not copied to target dist
> -------------------------------------------------------------
>                 Key: HADOOP-12556
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12556
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Babak Behzad
>            Assignee: Babak Behzad
>         Attachments: HADOOP-12556.patch
> There is a hadoop-kafka artifact missing from hadoop-tools-dist's pom.xml which was causing
the compiled Kafka jar files not to be copied to the target dist directory. The new patch
adds this in order to complete this fix.

This message was sent by Atlassian JIRA

View raw message