[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242771#comment-13242771
 ] 

Hudson commented on MAPREDUCE-4091:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #2031 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2031/])
    MAPREDUCE-4091. tools testcases failing because of MAPREDUCE-4082 (tucu) 
(Revision 1307623)

     Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1307623
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/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
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>            Priority: Critical
>             Fix For: 2.0.0
>
>         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

        

Reply via email to