[
https://issues.apache.org/jira/browse/MAPREDUCE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438658#comment-13438658
]
Hudson commented on MAPREDUCE-4091:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #350 (See
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/350/])
svn merge -c 1307124, 1307623, 1309583 FIXES: MAPREDUCE-4082 MAPREDUCE-4091
and MAPREDUCE-4097 hadoop-mapreduce-client-app's mrapp-generated-classpath file
should not be in the module JAR (tucu) (Revision 1375190)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1375190
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/pom.xml
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/util/TestMRApps.java
* /hadoop/common/branches/branch-0.23/hadoop-project/pom.xml
> tools testcases failing because of MAPREDUCE-4082
> -------------------------------------------------
>
> Key: MAPREDUCE-4091
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4091
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: build, test
> Affects Versions: 2.0.0-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Critical
> Fix For: 0.23.3, 2.0.0-alpha
>
> Attachments: MAPREDUCE-4091.patch
>
>
> MAPREDUCE-4082 moved the generated-classpath file used by MRApp from the main
> classpath to the test classpath.
> The objective of MAPREDUCE-4082 was to remove the generated-classpath file
> from the hadoop-mapreduce-client-app JAR. I've thought that moving it to the
> test-classpath would do the trick.
> This is breaking tools testcases (most likely) because of different
> classloader being used by maven for main classpath and test classpath.
--
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
