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

Hudson commented on HADOOP-16046:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15793 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/15793/])
HADOOP-16046. [JDK 11] Correct the compiler exclusion of (tasanuma: rev 
27aa6e8899782460d37ee03ba9a760371559f097)
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/pom.xml


> [JDK 11] Correct the compiler exclusion of 
> org/apache/hadoop/yarn/webapp/hamlet/** classes for >= Java 9 
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-16046
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16046
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Devaraj K
>            Assignee: Devaraj K
>            Priority: Major
>             Fix For: 3.3.0
>
>         Attachments: HADOOP-16046.patch
>
>
> I see that YARN-8123 handled it but still see that this fails with "mvn 
> compile".
> {code:xml}
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR] 
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/webapp/hamlet/HamletSpec.java:[306,20]
>  as of release 9, '_' is a keyword, and may not be used as an identifier
> ...............
> {code}
> {code:xml}
> [ERROR] 
> /hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/hamlet/TestHamlet.java:[40,24]
>  as of release 9, '_' is a keyword, and may not be used as an identifier
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to