[jira] [Updated] (YARN-8772) Annotation javax.annotation.Generated has moved

2018-09-13 Thread Andrew Purtell (JIRA)


 [ 
https://issues.apache.org/jira/browse/YARN-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated YARN-8772:
-
Attachment: YARN-8772.patch

> Annotation javax.annotation.Generated has moved
> ---
>
> Key: YARN-8772
> URL: https://issues.apache.org/jira/browse/YARN-8772
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: api
>Affects Versions: 3.1.1
>Reporter: Andrew Purtell
>Priority: Minor
> Attachments: YARN-8772.patch
>
>
> YARN compilation with Java 11 fails because the annotation 
> javax.annotation.Generated has moved. It is now 
> javax.annotation.processing.Generated. A simple substitution will break 
> compilation with older JDK, so it seems best to remove the annotations, which 
> are only documentation not functional.



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

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org



[jira] [Created] (YARN-8772) Annotation javax.annotation.Generated has moved

2018-09-13 Thread Andrew Purtell (JIRA)
Andrew Purtell created YARN-8772:


 Summary: Annotation javax.annotation.Generated has moved
 Key: YARN-8772
 URL: https://issues.apache.org/jira/browse/YARN-8772
 Project: Hadoop YARN
  Issue Type: Bug
  Components: api
Affects Versions: 3.1.1
Reporter: Andrew Purtell


YARN compilation with Java 11 fails because the annotation 
javax.annotation.Generated has moved. It is now 
javax.annotation.processing.Generated. A simple substitution will break 
compilation with older JDK, so it seems best to remove the annotations, which 
are only documentation not functional.



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

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org



[jira] [Updated] (YARN-1453) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments

2014-01-03 Thread Andrew Purtell (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated YARN-1453:
-

Attachment: 1453-trunk.patch
1453-branch-2.patch

Updated patches refreshed to latest trunk and branch-2.

 [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
 -

 Key: YARN-1453
 URL: https://issues.apache.org/jira/browse/YARN-1453
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 3.0.0, 2.4.0
Reporter: Andrew Purtell
Priority: Minor
 Attachments: 1453-branch-2.patch, 1453-branch-2.patch, 
 1453-trunk.patch, 1453-trunk.patch


 Javadoc is more strict by default in JDK8 and will error out on malformed or 
 illegal tags found in doc comments. Although tagged as JDK8 all of the 
 required changes are generic Javadoc cleanups.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Created] (YARN-1453) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments

2013-11-27 Thread Andrew Purtell (JIRA)
Andrew Purtell created YARN-1453:


 Summary: [JDK8] Fix Javadoc errors caused by incorrect or illegal 
tags in doc comments
 Key: YARN-1453
 URL: https://issues.apache.org/jira/browse/YARN-1453
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 3.0.0, 2.3.0
Reporter: Andrew Purtell
Priority: Minor
 Attachments: 1453-branch-2.patch, 1453-trunk.patch

Javadoc is more strict by default in JDK8 and will error out on malformed or 
illegal tags found in doc comments. Although tagged as JDK8 all of the required 
changes are generic Javadoc cleanups.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (YARN-1453) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments

2013-11-27 Thread Andrew Purtell (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated YARN-1453:
-

Attachment: 1453-branch-2.patch
1453-trunk.patch

 [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments
 -

 Key: YARN-1453
 URL: https://issues.apache.org/jira/browse/YARN-1453
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 3.0.0, 2.3.0
Reporter: Andrew Purtell
Priority: Minor
 Attachments: 1453-branch-2.patch, 1453-trunk.patch


 Javadoc is more strict by default in JDK8 and will error out on malformed or 
 illegal tags found in doc comments. Although tagged as JDK8 all of the 
 required changes are generic Javadoc cleanups.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Commented] (YARN-429) capacity-scheduler config missing from yarn-test artifact

2013-03-05 Thread Andrew Purtell (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594247#comment-13594247
 ] 

Andrew Purtell commented on YARN-429:
-

Thanks for looking into this. +1 on patch.

 capacity-scheduler config missing from yarn-test artifact
 -

 Key: YARN-429
 URL: https://issues.apache.org/jira/browse/YARN-429
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.0.3-alpha
Reporter: Siddharth Seth
Assignee: Siddharth Seth
Priority: Blocker
 Attachments: YARN-429.txt


 MiniYARNCluster and MiniMRCluster are unusable by downstream projects with 
 the 2.0.3-alpha release, since the capacity-scheduler configuration is 
 missing from the test artifact.
 hadoop-yarn-server-tests-3.0.0-SNAPSHOT-tests.jar should include the default 
 capacity-scheduler configuration. Also, this doesn't need to be part of the 
 default classpath - and should be moved out of the top level directory in the 
 dist package.

--
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