[
https://issues.apache.org/jira/browse/MAPREDUCE-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173747#comment-13173747
]
Tom White commented on MAPREDUCE-3378:
--------------------------------------
Scott, thanks for the great feedback! To summarize, we should do the following
(highest priority first):
1. Make sure that the transitive dependencies are correct for the artifacts
that we publish.
2. Publish client API JARs and document how to use them.
3. Possibly publish a 'fat jar' for all of Hadoop, but it should have a
different classifier.
Currently in 0.23 the situation for 2 is that hadoop-mapreduce-client-core
contains the API, hadoop-mapreduce-client-common contains the local job runner,
and hadoop-mapreduce-client-jobclient contains the YARN client, but they all
pull in too many dependencies (1). I've just noticed that
hadoop-mapreduce-client-core depends on HDFS classes, which isn't right.
> Create a single 'hadoop-mapreduce' Maven artifact
> -------------------------------------------------
>
> Key: MAPREDUCE-3378
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3378
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.23.0
> Reporter: Tom White
> Attachments: MAPREDUCE-3378.patch
>
>
> In 0.23.0 there are multiple artifacts (hadoop-mapreduce-client-app,
> hadoop-mapreduce-client-common, hadoop-mapreduce-client-core, etc). It would
> be simpler for users to declare a dependency on hadoop-mapreduce (much like
> there's hadoop-common and hadoop-hdfs). (This would also be a step towards
> MAPREDUCE-2600.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
