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

Hudson commented on YARN-181:
-----------------------------

Integrated in Hadoop-Hdfs-trunk #1205 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1205/])
    YARN-181. Fixed eclipse settings broken by capacity-scheduler.xml move via 
YARN-140. Contributed by Siddharth Seth. (Revision 1401504)

     Result = FAILURE
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1401504
Files : 
* 
/hadoop/common/trunk/hadoop-assemblies/src/main/resources/assemblies/hadoop-yarn-dist.xml
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/conf/capacity-scheduler.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/conf
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/conf/capacity-scheduler.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/pom.xml

                
> capacity-scheduler.xml move breaks Eclipse import
> -------------------------------------------------
>
>                 Key: YARN-181
>                 URL: https://issues.apache.org/jira/browse/YARN-181
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.2-alpha
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>            Priority: Critical
>             Fix For: 2.0.3-alpha
>
>         Attachments: YARN181_jenkins.txt, YARN181_postSvnMv.txt, 
> YARN181_svn_mv.sh
>
>
> Eclipse doesn't seem to handle "testResources" which resolve to an absolute 
> path. YARN-140 moved capacity-scheduler.cfg a couple of levels up to the 
> hadoop-yarn project.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to