[
https://issues.apache.org/jira/browse/MAPREDUCE-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172822#comment-13172822
]
Alejandro Abdelnur commented on MAPREDUCE-3378:
-----------------------------------------------
About repackaging multiple JARs into a single one, I see the following issues
with this:
* Developers unknowingly adding (other versions) of the grouped JARs to the
classpath.
* AFAIK there is not POM for the aggregate JARs with all the correct
dependencies.
IMO the root issue is that we are not using dependencies correctly.
There should be a hadoop-client that allows me to code and run HDFS/MR client
apps (with the exact set of transitive dependencies, ie you don't need jetty
stuff there).
There should be a hadoop-test that allows me to run run HDFS/MR minicluster for
integration testing.
The fact that under the hood these 'hadoop-client' & 'hadoop-test' component
pull 1 or 100 hadoop JARs is irrelevant (although IMO I think we have too many
JARs).
> 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
