[
https://issues.apache.org/jira/browse/HADOOP-12556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169320#comment-15169320
]
Allen Wittenauer commented on HADOOP-12556:
-------------------------------------------
cc: [~cnauroth] since I think he'll be interested as well.
The more and more I think about this situation and others (e.g., HADOOP-12721),
the more and more I'm inclined hadoop-tools-dist needs to be revisited now that
it's getting more and more case-specific content. With the existence of shell
profiles in trunk, this gets significantly easier...
Two potential options:
* break apart hadoop-tools-dist into multiple directories. create a shell
profile that sucks that functionalities entire dir.
* keep hadoop-tools-dist as one big dir (thus making it bw compat, but still
potentially messy). build a tool that creates shell profiles based upon the
maven dependency trees to list the specific jars needed by that functionality.
In both cases, to activate, simply copy shellprofile.d/foo.sh.example to
HADOOP_CONFIG_DIR/shellprofile.d/foo.sh. Or uncomment. Or whatever. In the
end, the shellprofile will add only the necessary components to the classpath.
And since it is being done via shell profiles a) those jars will always be
present, b) it doesn't interfere with any of the other env var settings that
users typically modify, c) should be bw compat with the entire universe so long
as they honor the output of the various classpath commands
> 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
(v6.3.4#6332)
