[
https://issues.apache.org/jira/browse/MAPREDUCE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129846#comment-13129846
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3087:
----------------------------------------------------
I've been conveniently ignoring this all this while.
mr-generated-classpath needs to be automatically generated. And it(its content)
is tied to the app module
(hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/pom.xml).
We cannot check-in some version of it; if something changes in app module,
this file(and/or the test-jar) needs to change and thus is unmaintainable.
So we should only add the real-app jar as the dependency. We only need it to be
present for jobclient module which uses the setFrameWorkClasspath() util, which
already is there.
So in sum, your patch without any pom changes should work for you, I think.
Shouldn't it?
> CLASSPATH not the same after MAPREDUCE-2880
> -------------------------------------------
>
> Key: MAPREDUCE-3087
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3087
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Priority: Critical
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-3087.patch, MAPREDUCE-3087.patch,
> MAPREDUCE-3087.patch, MAPREDUCE-3087.patch, notworking.classpath.uniq,
> test-mr-app.jar, working.classpath.uniq
>
>
> After MAPREDUCE-2880, my classpath was missing key jar files.
--
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
