[
https://issues.apache.org/jira/browse/MAPREDUCE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Prakash updated MAPREDUCE-3087:
------------------------------------
Attachment: MAPREDUCE-3087.patch
Arun. It was a blocker for me to do any dev work because all my jobs were
failing
I don't know if we ever want to have something in the CLASSPATH which doesn't
make sense to the JVM, and /somepath/mr-apps.jar!/mrapp-generated-classpath
doesn't make sense to the JVM (so it will be ignored).
Please ignore the last patch. It was an attempt to include tests, but it seems
pretty hard because:
1. If I include the real mr-app.jar (using pom.xml), then a circular dependency
is created.
2. If I don't include the mr-app.jar, then I must checkin and include in the
CLASSPATH some jar containing a file mrapp-generated-classpath. This seemed too
much effort for a simple one line change.
I'm re-uploading the 1st patch with is a single line change.
> 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
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-3087.patch, MAPREDUCE-3087.patch,
> MAPREDUCE-3087.patch, notworking.classpath.uniq, 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
