[jira] [Commented] (HADOOP-9616) In branch-2, baseline of Javadoc Warnings (specified in test-patch.properties) is mismatch with Javadoc warnings in current codebase
[ https://issues.apache.org/jira/browse/HADOOP-9616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676087#comment-13676087 ] Luke Lu commented on HADOOP-9616: - Verified the patch with test-patch on branch-2 using a trivial patch. +1. Will commit shortly. In branch-2, baseline of Javadoc Warnings (specified in test-patch.properties) is mismatch with Javadoc warnings in current codebase - Key: HADOOP-9616 URL: https://issues.apache.org/jira/browse/HADOOP-9616 Project: Hadoop Common Issue Type: Bug Affects Versions: 2.0.4-alpha Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-9616.patch, patchJavadocWarnings-new.txt, patchJavadocWarnings-old.txt Now the baseline is set to 13 warnings, but they are 29 warnings now. 16 warnings belongs to using Sun proprietary APIs, and 13 warnings is using incorrect link in doc. I think we should at least fix 13 warnings and set the baseline to 16. -- 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
[jira] [Commented] (HADOOP-9616) In branch-2, baseline of Javadoc Warnings (specified in test-patch.properties) is mismatch with Javadoc warnings in current codebase
[
https://issues.apache.org/jira/browse/HADOOP-9616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13674187#comment-13674187
]
Hadoop QA commented on HADOOP-9616:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12586073/patchJavadocWarnings-new.txt
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2598//console
This message is automatically generated.
In branch-2, baseline of Javadoc Warnings (specified in
test-patch.properties) is mismatch with Javadoc warnings in current codebase
-
Key: HADOOP-9616
URL: https://issues.apache.org/jira/browse/HADOOP-9616
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 2.0.4-alpha
Reporter: Junping Du
Assignee: Junping Du
Attachments: HADOOP-9616.patch, patchJavadocWarnings-new.txt,
patchJavadocWarnings-old.txt
Now the baseline is set to 13 warnings, but they are 29 warnings now. 16
warnings belongs to using Sun proprietary APIs, and 13 warnings is using
incorrect link in doc. I think we should at least fix 13 warnings and set the
baseline to 16.
--
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
[jira] [Commented] (HADOOP-9616) In branch-2, baseline of Javadoc Warnings (specified in test-patch.properties) is mismatch with Javadoc warnings in current codebase
[ https://issues.apache.org/jira/browse/HADOOP-9616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13674192#comment-13674192 ] Junping Du commented on HADOOP-9616: This patch is for branch-2 only so cannot applied on jenkins of trunk. In branch-2, baseline of Javadoc Warnings (specified in test-patch.properties) is mismatch with Javadoc warnings in current codebase - Key: HADOOP-9616 URL: https://issues.apache.org/jira/browse/HADOOP-9616 Project: Hadoop Common Issue Type: Bug Affects Versions: 2.0.4-alpha Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-9616.patch, patchJavadocWarnings-new.txt, patchJavadocWarnings-old.txt Now the baseline is set to 13 warnings, but they are 29 warnings now. 16 warnings belongs to using Sun proprietary APIs, and 13 warnings is using incorrect link in doc. I think we should at least fix 13 warnings and set the baseline to 16. -- 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
