This occurred because of
http://issues.apache.org/jira/browse/HADOOP-2289
Hudson tested selectCommand.patch (as can be seen from Hadoop QA's
comment), but selectCommand_v02.patch was the patch that was later
attached and committed.
Edward Yoon has already uploaded a javadoc.patch for this problem to
HADOOP-2289.
On Nov 27, 2007, at 8:47 AM, Adrian Woodhead (JIRA) wrote:
[ https://issues.apache.org/jira/browse/HADOOP-2290?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Woodhead updated HADOOP-2290:
------------------------------------
Status: Patch Available (was: Open)
Patch to hopefully fix issue.
As an aside, shouldn't Hudson apply the same strict rules to
commits for commiters as it does to patches? Then this might not
have got through?
hbse CreateCommand.java is causing javadoc errors which is causing
hudson to fail patches
---------------------------------------------------------------------
--------------------
Key: HADOOP-2290
URL: https://issues.apache.org/jira/browse/
HADOOP-2290
Project: Hadoop
Issue Type: Improvement
Components: contrib/hbase
Affects Versions: 0.16.0
Reporter: Adrian Woodhead
Attachments: HADOOP-2290-1.patch
Running javadoc on fresh checkout from trunk causes the following
error:
[javadoc] /home/adrian/workspace/hadoop-trunk/src/contrib/hbase/
src/java/org/apache/hadoop/hbase/shell/CreateCommand.java:77:
warning - @param argument "table" is not a parameter name.
This is causing Hudson to report a -1 for all patches, even though
they have nothing to do with this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
